Taming the Monolith
2 likes633 views
The document discusses the concepts of microservices and domain modeling, emphasizing the importance of a ubiquitous language shared by all team members. It introduces the idea of bounded contexts and outlines key attributes of both microservices and bounded contexts, focusing on high cohesion and loose coupling. The author argues that models should represent useful abstractions rather than aim for universal application.
Taming the Monolith
- 1. TAMING THE MONOLITH Are microservices just an implementation detail? #GOTOnight Cologne | June 22nd, 2015 | Dennis Traub | @DTraub
- 2. EVERYBODY TALKS ABOUT MICROSERVICES 2
- 6. - A sphere of knowledge, influence, or activity - - What an organisation does, and the world it does it in - DOMAIN
- 7. - A system of abstractions describing selected aspects of a Domain - - Used to solve problems related to that Domain - MODEL
- 8. SIT DOWN WITH THE EXPERTS & LISTEN
- 11. - A language structured around the Domain Model - - Used by all team members and throughout the code - UBIQUITOUS LANGUAGE
- 12. Customer
- 17. Customer Recipient ShippingMarketing Target Group Hotline Caller Website Visitor Shopping Cart Buyer
- 19. - An explicit boundary within which a Domain Model exists - - Inside, all terms have a specific meaning - - They are part of the Ubiquitous Language - BOUNDED CONTEXT
- 22. KEY ATTRIBUTES OF A BOUNDED CONTEXT High Cohesion Loose Coupling Represents Business Capability Context-specific Model
- 23. KEY ATTRIBUTES OF A MICROSERVICE High Cohesion Loose Coupling Represents Business Capability Context-specific Model
- 24. We don’t model reality We model useful abstractions
- 25. We don’t build a model that works for everyone
- 26. THANK YOU! Dennis Traub | @DTraub | #GOTOnight