DDD encompasses a range of techniques from high-level Event Storming for understanding the domain to tactical design for implementing classes and aggregates.
Instead of aiming for uniform high quality, strategically focus development effort and refinement on the core domain, which is the most critical part of the system.
Domain-Driven Design is not just a set of coding rules but a comprehensive approach to software engineering that addresses different concerns for various roles like developers and architects.
The primary goal of applying DDD is to deliver value to the customer, which requires developers to actively engage with users and domain experts to understand their needs.
Collaborative modeling techniques like Event Storming lower the barrier to participation, enabling better knowledge crunching and shared understanding between technical teams and domain experts.
A Bounded Context is a core DDD pattern that defines the boundary for a specific domain model, its associated ubiquitous language, and often the scope of a single team.
Design modules around business functionality rather than shared data entities to create highly autonomous systems with low coupling.
The talk concludes by reinforcing that DDD is about letting the domain drive design, using collaboration to understand it, and building autonomous modules.
43:13Carola Lilienthal
29:54Hendrik Lösch
1:01:30Henning Schwentner
22:45Abiodun Olowode
34:36Werner Vogels
25:05Eberhard Wolff
26:22David Tielke
29:25Matthias Niehoff
Jobs that call for the skills explored in this talk.
Multiplied
Nootdorp, Netherlands
