Taming the Monolith - Microservices Meetup Hamburg
•
1 like•1,160 views
Taming the Monolith - Are Microservices just an Implementation Detail? The slides of my presentation at the Microservices Meetup Hamburg on July 13th, 2015, hosted by Adobe Systems Engineering GmbH. Event details: http://www.meetup.com/de/Microservices-Meetup-Hamburg/events/220839035/
Report
Share
Taming the Monolith - Microservices Meetup Hamburg
- 1. TAMING THE MONOLITH Are microservices just an implementation detail? Microservice Meetup Hamburg | July 13th, 2015 | Dennis Traub | @DTraub
- 2. EVERYBODY TALKS ABOUT MICROSERVICES 2
- 8. - A sphere of knowledge, influence, or activity - - What an organisation does, and the world it does it in - DOMAIN
- 9. - A system of abstractions describing selected aspects of a Domain - - Used to solve problems related to that Domain - MODEL
- 10. Sit down with the experts and listen
- 13. - A language structured around the Domain Model - - Used by all team members and throughout the code - UBIQUITOUS LANGUAGE
- 14. There is no such thing as a Ubiquituous Language … at least not company-wide …
- 15. Customer
- 20. Customer Recipient ShippingMarketing Target Group Hotline Caller Website Visitor Shopping Cart Buyer
- 24. - 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
- 25. KEY ATTRIBUTES OF A BOUNDED CONTEXT High Cohesion Loose Coupling Represents Business Capability Context-specific Model
- 26. KEY ATTRIBUTES OF A MICROSERVICE High Cohesion Loose Coupling Represents Business Capability Context-specific Model
- 28. Business Logic Data Access Presentation our “Architecture”
- 29. Business Logic Data Access Presentation our “Architecture”
- 30. Business Logic Data Access Presentation our “Architecture”
- 31. Business Logic Data Access Presentation our “Architecture”
- 36. Key Takeaways:
- 37. Don’t model reality. Model useful abstractions.
- 38. Don’t build a model. that works for everyone.
- 39. Don’t design a one-size-fits-all architecture.
- 40. So, what are Microservices all about?
- 41. THANK YOU! Dennis Traub | @DTraub | ThoughtWorks.com