Download as PDF, PPTX
Uploaded byTrond Hjorteland
Microservices without DDD is risky business!
The document discusses the importance of modularization and service-oriented architecture in software development, emphasizing the need for domain-driven design (DDD) as a mindset for better understanding business domains. Key principles include the autonomy of services, explicit service boundaries, and collaboration between software and domain experts. Additionally, it highlights various subdomains and tactical patterns within DDD to enhance system flexibility and development efficiency.
Microservices without DDD is risky business!
- 1. Making IT yourwinning asset
- 2. Trond Hjorteland Partner atscienta.no @trondhjort
- 3. Microservices without DDDis risky business!
- 4.
- 5. Imposter syndrome Source: DavidWhittaker @rundavidrun What I think others know What I know What I know What others know @trondhjort
- 6.
- 8. “This _____ discussesmodularisation as a mechanism for improving the flexibility and comprehensibility of a system while allowing the shortening of its development time.” @trondhjort -David Parnas, 1972 paper
- 9. Source: D.L. Parnas,Communications of the ACM, 1972
- 11. Source: “From Capabilitiesto Services…”, Ulrich Homann & Jon Tobey 2006@trondhjort
- 13.
- 14.
- 15.
- 16. Service-orientation Boundaries are explicit Servicesare autonomous Services share schema and contract, not class Service compatibility is based on policy s @trondhjort
- 18.
- 19. "DDD, for me,is a mindset, a journey, a way of ‘learning’ more about a business domain and its problem, not a destination or an artefact in some code base.” @trondhjort
- 20. Collaboration of softwareand domain experts Focus on the core domain Ubiquitous language in a bounded context The essence of DDD @trondhjort Source: Domain-Driven Design Reference
- 21. Strategic patterns Source: Domain-DrivenDesign Reference@trondhjort
- 22. Source: Patterns, Principlesand Practices of Domain-Driven Design@trondhjort
- 23. Source: Ulrich Kalex,The Open Group@trondhjort
- 24. Subdomains Customer Account Subscription Billing Customer Care Subscription Management Billing Account Customer Subscription Portfolio OwnerPayer Sales Invoice Install base Products @trondhjort
- 25. “All models arewrong but some are useful” -George Box Source: Robustness in Statistics, 1978@trondhjort
- 26. Source: Implementing Domain-DrivenDesign@trondhjort
- 27.
- 28. Tactical patterns Source: Domain-DrivenDesign Reference@trondhjort
- 29.
- 30. Subdomain ⊇ Service(BC) ⊇ Aggregate Subscription Portfolio Owner Portfolio management ⊇ Taxonomy Portfolio Subscription A Subscription B Subscription C ⊇ @trondhjort
- 31. Delivery approaches Top-down Bottom-up Architecture principles InverseConway Manoeuvre @trondhjort
- 32.
- 33.
- 35.