Domain Driven Design

Transcript

1. DOMAIN DRIVEN DESIGN DDD
2. BY ERIC EVANS
3. 150 PAGES
4. WHAT IS DOMAIN? • Business or whatever activity we are trying to assist with the software
5. • Assembly parts != Car • Vision • Specification • Architecture
6. • Communication between experts & developers • Develop model together
7. UBIQUITOUS LANGUAGE • Model driven: Based on the Domain Model • Building up a common, rigorous language between developers and users • UML • Software doesn't cope well with ambiguity
8. BOUNDED CONTEXT • Model gets bigger • Bound context • Domain & sub domain Domain Sub Domain Service Sub Domain Service Sub Domain Service
9. • Product in Catalog domain • Product in Stock Management domain Product image, title, price product code, storage
10. • Subdomain has its own model • Each model has bounded context
11. BUILDING BLOCKS Model Driven Development
12. LAYERED ARCHITECTURE
13. ENTITY • Not defined by their attributes • Continuity • Identity
14. VALUE OBJECT • These objects describe characteristics of a thing. • Immutable during lifecycle
15. SERVICE • oo manger • significant process or transformation in the domain is not a responsibility of an ENTITY or VALUE OBJECT, add SERVICE • The interface is defined in terms of other elements in the domain model • Stateless
16. MODULE • Highly cohesive • Low coupling • Derived from the Ubiquitous Language
17. AGGREGATE • Logical boundary for things that can change in a business transaction of a given context. • Reduce many to many relationship • Root: outside objects holds references to
18. AGGREGATE
19. FACTORY • Produces complicated aggregates or sometimes also entities and value objects
20. REPOSITORY • Interfaces for storing and retrieving Aggregate Roots
21. • Refactoring • Maintaining model integrity • …
22. THANK YOU!