Domain Driven Design
Download as PPTX, PDF4 likes1,156 views
The document discusses domain-driven design (DDD) and its advantages. It explains that DDD focuses development around modeling a problem domain to address the complexity of different characters communicating in different languages. It advocates developing a shared language and domain model so that everybody involved talks using the same terminology. This improves cohesion, isolates domain logic, and makes the solution more robust and less brittle.
Domain Driven Design
- 1. Lalit Kalee-Zest Solutions Ltd.Domain Driven Design
- 2. Problem
- 4. ProblemDiverse Characters to solve one problemEverybody talks in different languageUltimate Result- Delivered solution is brittle and Fragile
- 5. Everybody who are involved should talk in one LanguageStep 1 : Agree on language terminology and definitionsStep 2: Call on the language expertStep 3 : Use Business model to device the languageSolution
- 6. Domain: “Afield of study that defines a set of common requirements, terminology, and functionality for any software program constructed to solve a problem in that field “.Driven: Focused onDomain Driven Development
- 7. Domain: “Afield of study that defines a set of common requirements, terminology, and functionality for any software program constructed to solve a problem in that field “. = Problem DomainDomain Model: The domain model is a rigorously organized and selective abstractionsof knowledge’Domain Driven Development
- 8. Traditional ArchitecturePresentationBusiness LayerInfrastructure/Utility/LibraryData Access (DAL)
- 9. DDD ArchitectureUser InterfaceApplication ServicesMDomain ServicesDatabaseDomain ModelServicesFilesystemTestsInfrastructureetc
- 10. DDD ArchitectureUser InterfaceApplication ServicesMDomain ServicesDatabaseDomain ModelServicesFilesystemTestsInfrastructureetc
- 13. Bounded Contexts
- 15. Refactoring
- 16. Command Query Separation (CQS)
- 17. When to use DDD
- 18. When NOT to Use DDD
- 19. Patterns
- 20. Entities
- 21. Value Objects
- 22. Aggregate Roots
- 24. Repository
- 25. Specification
- 26. Domain Services
- 27. Modules
- 28. Domain Events
- 30. DDD Fundamentals-EntityObjects that have a distinct identity that runs through time and different representations. You also hear these called "reference objects".Entities are usually big things like
- 31. DDD Fundamentals-Value ObjectsA small simple object, like money or a date range, whose equality isn't based on identity.Value Objects are usually small things (Hidden concepts in system) like
- 32. DDD Fundamentals- Aggregate RootsAn Aggregate comprises of an intimately associated group of Entities and Value ObjectsAggregates are treated as a single unit for the purpose of persistence, and references are only allowed to the Aggregate Root
- 33. DDD In Practice
- 34. Without DDD
- 36. Promotes high cohesion and low coupling Easy to test domain components Business (domain) logic is isolated from non-domain and infrastructure code Adding/changing services does not influence the domain or other services.Everybody talks on same termsAdvantages