Downloaded 145 times
Uploaded byEberhard Wolff
How to Split Your System into Microservices
This document discusses the concept of microservices, emphasizing their role as independent modules that facilitate decoupled feature development by separate teams. It outlines the importance of defining bounded contexts to achieve effective architecture and scalability, while also addressing challenges in transitioning existing architectures to microservices. Additionally, it highlights technical reasons for implementing microservices, including independent scalability and efficient handling of legacy systems.
In this document
Powered by AI
Introduction to the topic by Eberhard Wolff. A focus on splitting systems into microservices.
Definition of microservices as independent deployment units aimed at decoupling.
Discusses why splitting services is crucial, outlining benefits and potential goals.Details various scenarios and how they influence the splitting of microservices.
Introduction to 'bounded context' as a key concept in designing microservices architecture.
Discusses challenges of creating bounded contexts based on coherence and independence.Recommends organizing microservices around use cases for better independence.
Evaluates how existing architecture impacts transitioning to microservices.
Integrating external systems into microservices to simplify data management.
Technical justifications for microservices including independent scalability.
The implications of requirements on the design and independence of microservices.
Summarizes key points about microservices, their frameworks, and integration results.
More Related Content
Similar to How to Split Your System into Microservices
How to Split Your System into Microservices
- 1. How to SplitYour System into Microservices Eberhard Wolff @ewolff Fellow
- 2.
- 3.
- 4.
- 6. Microservices: Definition > No consistentdefinition > Microservices are modules > Independent deployment units > E.g. Docker container > Microservice owned by one team
- 7. Microservices: Definition Server / Container Server/ Container Micro Service Micro Service
- 8.
- 9. Why is theSplit so Important? > Microservices implement a part of the logic > Allow isolated development of features > …and independent teams > If split is wrong, you won’t achieve goals. > …and there is just more complexity. > But there are even more goals!
- 10. Why Microservices? Strong Modularization ScalingAgile Sustainable development Replaceable Services Continuous Delivery Free choice of technology Handle Legacy efficient Independent Scaling Robustness Small teams develop and deploy independently Add services – not code Small Services Failure limited to single Microservice
- 11. Why Microservices? Scaling Agile Sustainabledevelopment Continuous Delivery Free choice of technology Handle Legacy efficient Independent Scaling Robustness Organization Deployment Units Technology
- 12. There are many reasonsfor microservices.
- 13. There are many scenariosfor microservices.
- 14. Scenario and reason influencethe split.
- 15.
- 17.
- 18.
- 19.
- 20.
- 21.
- 22. A domain model isonly useful in a BOUNDED CONTEXT.
- 23. There is no universaldata model in a large system.
- 24.
- 25. Address for calculating the drones’routes VALUE OBJECT ENTITYor
- 26.
- 27.
- 31. Why would youbuild a universal data model if that is neither possible nor useful??
- 32. Bounded Context: Challenge > Nota way to design a great architecture > …but consequence of good domain architecture > i.e. clearly separated domains will lead to separated BOUNDED CONTEXTS > …containing logic and data > How can you find BOUNDED CONTEXTS?
- 33. Bounded Context: Challenge > Coarse-grained >Ideal: implement a functionality in one unit > Ideal: Independence > Might have relationships > …limiting independence
- 34. Divide by UseCases > Microservice should implement a use case > …ideally without calling other microservices > Divide use cases among microservices > …then decide about the BOUNDED CONTEXT
- 35. BrowsingRegistration Creating Microservices User RegistrationSearch Products by Keywords Browse Products by Category Checkout Payment Define ShipmentUpdate Profile Basic customer data Preferences Recommendations Billing address Payment information All these services have data about the customer!!
- 36. Bounded Context Scaling Agile Sustainabledevelopment Continuous Delivery Free choice of technology Handle Legacy efficient Independent Scaling Robustness Organization Deployment Units Technology
- 37.
- 38. Existing Architecture Product CustomerWarehouse Product Service Customer Service Warehouse Service iOS Android PoS Web
- 39. Let’s create some BoundedContexts!
- 40. Existing Architecture Product CustomerWarehouse Product Service Customer Service Warehouse Service iOS Android PoS Web Browsing
- 41. Bounded Contexts > Browsingdistributed in many artifacts > Change to Browsing might influence all of them > …or not > BOUNDED CONTEXTS would be desirable
- 42. Migrate to BoundedContext Product Customer Warehouse Product Service Customer Service Warehouse Service iOS Android PoS Web BrowsingBrowsing
- 43. Introducing Bounded Contexts > …wouldchange the architecture completely > …might be very hard > …and risky > Is it worth it? > Is it even doable? > Might also change the organization
- 44. Add services Product CustomerWarehouse Product Service Customer Service Warehouse Service iOS Android PoS Web
- 45. Add services Product CustomerWarehouse Product Service Customer Service Warehouse Service iOS Android PoS Web News- letter Web
- 46. Add Service > Mightreplace the old system stepwise > Immediate benefits > Low risk > Major reason for microservices
- 47. Cut existing services ProductCustomer Warehouse Product Service Customer Service Warehouse Service iOS Android PoS Web
- 48. Existing Architecture Scaling Agile Sustainabledevelopment Continuous Delivery Free choice of technology Handle Legacy efficient Independent Scaling Robustness Organization Deployment Units Technology
- 49. Existing Architecture > ...hasan impact on the target architecture > What good is an architecture you cannot migrate into? > Might overrule everything else > Even BOUNDED CONTEXT
- 50. BrowsingRegistration External Systems User RegistrationSearch Products by Keywords Browse Products by Category Checkout Payment Define ShipmentUpdate Profile Browse Products by Category Payment Provider Logistic Partner
- 51. BrowsingRegistration External Systems User RegistrationSearch Products by Keywords Browse Products by Category Checkout Update Profile Browse Products by Category Payment Provider Logistic Partner Payment Shipping
- 52. External Systems > Limitintegration for each external system to one Microservice > External system might belong to a domain > …or BOUNDED CONTEXT > ...or not > Simplifies integration > Easier to achieve robustness
- 53. External Systems Scaling Agile Sustainabledevelopment Continuous Delivery Free choice of technology Handle Legacy efficient Independent Scaling Robustness Organization Deployment Units Technology
- 54. We expect a lotmore registrations!
- 55. BrowsingRegistration External Systems User RegistrationSearch Products by Keywords Browse Products by Category Checkout Payment Define ShipmentUpdate Profile Browse Products by Category
- 56. BrowsingRegistration External Systems Search Products byKeywords Browse Products by Category Checkout Payment Define ShipmentBrowse Products by Category Regis- tration Update Profile
- 57. Technical Reasons > Independentscalability is just one technical reason > There are many more > Might be OK to share database in this scenario > Might even split read and write
- 58. CQRS > Command –Query Responsibility Segregation > Commands change data > Query provide data > Implement in separate microservices
- 59.
- 60. Technical Reasons Scaling Agile Sustainabledevelopment Continuous Delivery Free choice of technology Handle Legacy efficient Independent Scaling Robustness Organization Deployment Units Technology
- 61. Registration Requirements Browsing Checkout Marketing SalesFulfillment Finance
- 62. Requirements > One microserviceshould implement one stream of requirements > Otherwise: coordinate priorities > …and therefore less independence
- 63. Registration Requirements Browsing Payment Marketing SalesFulfillmentFinance Shipping
- 64. Requirements Scaling Agile Sustainable development ContinuousDelivery Free choice of technology Handle Legacy efficient Independent Scaling Robustness Organization Deployment Units Technology
- 65.
- 66.
- 67.
- 68. EMail [email protected] toget: Slides + Microservices Primer + Sample Microservices Book + Sample of Continuous Delivery Book Powered by Amazon Lambda & Microservices