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.

1. Lalit Kalee-Zest Solutions Ltd.Domain Driven Design

2. Problem

3. Problem- Characters Involved

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

11. DDD JargonConceptual

12. Ubiquitous Language

13. Bounded Contexts

14. Persistence Ignorance

15. Refactoring

16. Command Query Separation (CQS)

17. When to use DDD

18. When NOT to Use DDD

19. Patterns