Joseph’s Reviews > Domain Modeling Made Functional: Tackle Software Complexity with Domain-Driven Design and F# > Status Update
Joseph
is on page 25 of 312
Chapter 1 read. Takeaways are ubiquitous language, shared domain mental models, bounded contexts and their relationships represented by context maps (corresponding to subdomains), problem vs solution space, event storming, and domain events + workflows and their associated commands. DDD feels like an iteration on agile, cutting out intermediaries and focusing on collaboration. Core over supporting/generic domains.
— Dec 04, 2022 08:56PM
Like flag
Joseph’s Previous Updates
Joseph
is on page 43 of 312
End of chapter 2. Resist the urge to do database-driven or class-driven design. The presented text-based specification approach is appealing and captures all of our concerns in a way that remains readable by domain experts. Complexity can be captured early by listening to domain experts carefully. Ubiquitous language is crucial to ensure correct understanding between domain experts and devs.
— Jan 07, 2023 05:31AM
