Strategic DDD

Transcript

1. Strategic Domain-Driven Design
2. Requirements Telephone
4. Why Domain-Driven Design (DDD)? • A domain model and ubiquitous language provide a mechanism for shared understanding • The whole team gains a useful mental model for discussion & refinement, which leads to greater understanding of our business • Domain experts can contribute to software design, leading to a better representation of how the business works • Since pure models can be late bound to implementation details, they are easier to test, which leads to more correct implementations
5. Domains, Bounded Contexts & Ubiquitous Language
6. Problem Domains and Solution Contexts
9. Publishing Core Domain • Conceptualizing and proposing a book • Contracting with authors • Managing the book’s authorship and editorial process • Designing the book layout, including illustrations • Translating the book into other languages • Producing the physical print and/or electronic editions • Marketing the book • Selling the book to resellers and/or directly to consumers • Shipping a physical book to resellers and consumers
10. Ubiquitous Language
11. NOPE
12. Context Maps
13. Conway’s Law “Organizations which design systems ... are constrained to produce designs which are copies of the communication structures of these organizations.”
14. Big Ball of Mud
15. Partnerships
16. Shared Kernel
17. Customer-Supplier
18. Conformist
19. Anti-Corruption Layer
20. Open Host Service
21. Published Language
22. Separate Ways
27. Architectures
28. Layered Architecture
29. Layered Architecture using Dependency Inversion
30. Clean Architecture
31. Event-driven
32. Grid-based Distributed Computing
33. Pipes and Filters
34. Representational State Transfer (REST) • Uniform Interface • Client-Server • Stateless • Cacheable • Layered System • Code-on-demand (optional)
35. Key Takeaways • Shared understanding is a non-negotiable goal • The structure of the organization contributes to the structure of the codebase • Architecture is not implementation details, like which database or framework you are using, instead it is the structure of your system