January 2018
Beginner to intermediate
312 pages
7h 22m
English
We have completed our domain model and implementation, but we all know that that’s not the end of the story. It’s all too common for a domain model to start off clean and elegant; but as the requirements change, the model gets messy and the various subsystems become entangled and hard to test. So here’s our final challenge: can we evolve the model without it becoming a big ball of mud?
Domain-driven design is not meant to be a static, once-only process. It is meant to be a continuous collaboration between developers, domain experts, and other stakeholders. So if the requirements change, we must always start by reevaluating the domain model first, rather than just patching the implementation. ...
Read now
Unlock full access