Domaine Driven Design - Bordeaux IO
•
0 j'aime•1,827 vues
Introduction au principaux concepts de DDD avec un lien Github pour mettre en place ces derniers. Par Gérome Egron et Nicolas Jozwiak, consultants chez Xebia
Recommandé
Contenu connexe
Similaire à Domaine Driven Design - Bordeaux IO
Similaire à Domaine Driven Design - Bordeaux IO (20)
Plus de Publicis Sapient Engineering
Plus de Publicis Sapient Engineering (20)
Dernier
Dernier (20)
Domaine Driven Design - Bordeaux IO
- 1. Domain Driven Design Gérôme Egron ! Nicolas Jozwiak
- 2. Programmeur et agiliste! ! @njozwiak
- 3. Xebia consultant since 2012.! ! @geromeegron
- 4. SOMMAIRE • Domain Driven Design! ! • Les principaux concepts! ! • Architecture hexagonale! ! • Hands On!
- 6. REFERENCES
- 7. DOMAIN • Core business of the company! ! • Represents a sphere of knowledge! ! • Create best software by concentrating on the problems related to the domain!
- 8. DOMAIN • Not focus on technologies! ! • Ubiquitous language ! ! structured language around the domain model and used by all team members
- 9. MODEL DRIVEN DESIGN • Represents the domain model in terms of software! ! • Code modification means changing model! ! • Model is adapted to a usage, a context
- 10. PATTERNS
- 11. ENTITIES • entity = identity + state! ! • long lifecycle! • has to have an operational way of applying identity! • Identity has to be guaranted unique within the system
- 12. ENTITIES • The object state is the sum of its data values which define it at a precise moment in time! ! • Different stable state which occurs with transformations! ! • Mutable and immutable attributes!
- 13. VALUE OBJECTS • No conceptual identity! ! • Immutable! ! • Focus of their domain! ! • Reflect constraints!
- 14. VALUE OBJECTS • Help to define the state of other entities objects! ! • Construction has to be meaningful and well formed
- 15. VALUE OBJECTS • Make implicit concepts explicit void addCustomer(String, String) void addCustomer(Name, PhoneNumber)
- 16. AGGREGATES • Treats domain objects as a single unit! ! • Operations have to interfer with root! ! • Ensure integrity of the whole!
- 17. SERVICES • When a significant process or transformation in the domain is not a responsibility of an entity or value object! ! • Define an interface in terms of language of the model! ! • Have to be stateless!
- 18. SERVICE TYPES • Domain service! ! • Infrastructure service! ! • Application service
- 19. REPOSITORIES • Mediator between data access and domain layer! ! • Root entity
- 20. BOUNDED CONTEXT • Model has a limit! ! • Communication with others domains! ! • anticorruption layer! • conformist! • shared kernel! • customer/supplier relationship! • separate ways! • open host
- 21. ARCHITECTURE HEXAGONALE Port and Adapter
- 23. Port / Adapter Domain X
- 24. Port / Adapter Interface Repository / Mock
- 25. Port / Adapter Domain Rest Adapter Rest Port Queue Adapter Queue Port
- 26. Port / Adapter