Foundation of Domain-Driven Design
My latest article "The Foundation of Domain-Driven Design" will be published in the next edition of the Dutch SDN magazine which will appear on 17th of August. It will be available as a free download as well.
This article answers two fundamental questions. What is domain-driven design and why is it important for a developer?
After a short introduction I introduce you to three of my projects in which I applied DDD. I will share my experiences with a new medical examination application that should support the introduction of life insurance products. Secondly, we'll look at an application striving for operational excellence in the primary process of winning information from work relations and related remuneration components. Finally, we'll look at an application that allows for comprehensive product track and trace capability to enable fast investigation of product genealogy, including origins, involved processes, storage locations, and delivery points.
Then we'll look at "the right approach" for organizing domain logic (see an earlier attempt on this subject). What choices do we have and what do they imply? How are these choices related to the development process and what are the "prerequisites for applying DDD" to your own projects.
Next we'll determine the impact on team dynamics, create a common understanding of a model. Of course we'll focus on the hart of our software and why we tend to ignore it in real projects. What does it mean to create a ubiquitous language and what are common pitfalls in this area.
Enjoy!