Recommended
Recommended
More Related Content
Recently uploaded
Recently uploaded (20)
Featured
Featured (20)
Devs, let's reclaim DDD!
- 1. DEVS, LET'S RECLAIM DDD! Arnaud THIEFAINE Dorra BARTAGUIZ
- 2. WHY SHOULD WE LEARN DDD? It’s so stylish! I want to do like those who talk about it. For an awesome resume! It might be useful at the end! @ArnaudThiefaine @DorraBartaguiz
- 4. WHO ARE WE? Coach / trainer Co-author « Software Craft » ArnaudThiefaine athiefaine VP Tech @Arolla Co-author & illustrator « Software Craft » DorraBartaguiz iAmDorra Arnaud THIEFAINE Dorra BARTAGUIZ https://www.arolla.fr/training/
- 5. DOMAIN DRIVEN DESIGN 20 years @ArnaudThiefaine @DorraBartaguiz
- 6. SURVEY Do you know DDD? No 5% Yes, I know the name 28% Yes, I apply some concepts 42% Yes, I use it daily 25% @ArnaudThiefaine @DorraBartaguiz
- 7. Appreciate DDD ~56% Find it difficult to apply ~63% @ArnaudThiefaine @DorraBartaguiz
- 8. WHAT WE REPROACH THE DDD? I am not an architect, so I did not have the opportunity to dig I do not have access to the organization's strategic discussions The organization and the teams are too hermetic to make it It is mainly used to make bullshit diagrams It does not go back to the code @ArnaudThiefaine @DorraBartaguiz
- 9. SUMMARY • Modelling Kata (Theater Kata) • Value Object to rescue primitive-obsessions • Business and technic separation • Sandwich pattern • Hexagonal architecture • Bounded Contexts identification • Protect invariants • Aggregate • Entity • Value Object • Service & repository • Separate Bounded Contexts @ArnaudThiefaine @DorraBartaguiz
- 10. 50% VIP 35€ standard category +50% for premium THEATER KATA Beatriz « The CICD » @ArnaudThiefaine @DorraBartaguiz
- 11. THEATER KATA Side-by-side seats Loyalty card Tickets Premium category Alix books 4 seats @ArnaudThiefaine @DorraBartaguiz
- 18. IDENTIFICATION OF DIFFERENTS BUSINESS/DOMAINS Aka Bounded Contexts @ArnaudThiefaine @DorraBartaguiz
- 21. SJƆ & ING Seat reservation Marketing Performance scheduling Pricing Ticketing @ArnaudThiefaine @DorraBartaguiz
- 22. SJƆ & ING Seat reservation Marketing Performance scheduling Pricing Ticketing @ArnaudThiefaine @DorraBartaguiz
- 23. PERSONAE Beatriz, actress Julia, marketing Alix, client Director Terminal @ArnaudThiefaine @DorraBartaguiz
- 26. BC IDENTIFICATION HINTS • “/t/s/ion” sjɔ̃ • “ing” • Different personae • Synonyms • Words with multiple meanings @ArnaudThiefaine @DorraBartaguiz
- 27. HEXAGONAL ARCHITECTURE Not Domain Domain Adapters Ports API / exposition SPI / infra Mock infra not domain @ArnaudThiefaine @DorraBartaguiz
- 29. SPECIFICATION • Domain Invariant : predicat • Validate a domain objet using isSatisfiedBy() • Model a rule • Configurable Domain Specification @ArnaudThiefaine @DorraBartaguiz
- 31. REPOSITORY • Collection-oriented • Manage transaction • in repo not the service • Side Effect • Injectable • Ubiquitous language • For naming Domain Repository @ArnaudThiefaine @DorraBartaguiz
- 32. AGGREGATE • Unique identity for the grape • Aggregate Root • Invariant to protect • Consistence • validity • transactional (save/load) Domain Aggregate @ArnaudThiefaine @DorraBartaguiz
- 36. Value object No identity Value equality Immutable Parametrized Constructor Factory method Side-effect-free Entity Unique identity Evolves over time Domain Entity ValueObject @ArnaudThiefaine @DorraBartaguiz
- 39. THEATER TOPOLOGY Balcony 1 (premium) Balcony 2 (premium) Row E Row F Row G Row I Row J Row K Row A Row B Row C Row D Central zone (standard) @ArnaudThiefaine @DorraBartaguiz
- 40. THEATER TOPOLOGY Balcony 1 (premium) Balcony 2 (premium) Row E Row F Row G Row I Row J Row K Row A Row B Row C Row D Central zone (standard) @ArnaudThiefaine @DorraBartaguiz
- 41. THEATER TOPOLOGY Balcony 1 (premium) Balcony 2 (premium) Row E Row F Row G Row I Row J Row K Row A Row B Row C Row D Central zone (standard) @ArnaudThiefaine @DorraBartaguiz
- 42. SEAT ALLOCATION Row E Row F Row G Row I Row J Row K Row A Row B Row C Row D @ArnaudThiefaine @DorraBartaguiz
- 44. SERVICE • Stateless • Injectable • Business logic • Neither in Value Object • Nor in Entity • Ubiquitous language • For naming Domain Service Service @ArnaudThiefaine @DorraBartaguiz
- 45. Make sure you need a service. […] Using Services overzealously will usually result in the negative consequences of creating an Anemic Domain Model. - Vaughn Vernon Implementing Domain-Driven Design @ArnaudThiefaine @DorraBartaguiz
- 46. TO SUM UP Aggregate Aggregate root Entity Value object Service Repository Components (injectables) Domain model (instantiables) Specification @ArnaudThiefaine @DorraBartaguiz
- 49. UP TO YOU! • Rely on test coverage • Identify Bounded Contexts • Refactor in baby steps • Extract Value Object, Entities, • Aggregates, Repositories, Services • Promote naming @ArnaudThiefaine @DorraBartaguiz