Applying Domain-Driven Design and Patterns [ADDDP] is on its way
Finally, Applying Domain-Driven Design and Patterns [ADDDP] is on its way to the bookshops. I hope to get a copy before the 10th of June, since I’ll be on my way to Sardinia, Italy as of that day.
In Java the Domain Model pattern is the de facto standard for organizing domain logic whereas .NET still struggles with legacy in which it was very hard to execute this particular pattern. On top of that it has been made far too easy to work with in-memory tabular data. This led to the Table Module pattern being the dominant standard in our field. Martin Fowler introduced me to my current thinking that “logic” rarely fits any logical pattern which leads to the real benefit of objects. In his excellent book Pattern of Enterprise Application Architecture [PoEAA] he described the technical options for developing a good infrastructure. At that time Microsoft supplied guidance in the Designing Data Tier Components and Passing Data Through Tiers paper. Around that time Eric Evans collected his knowledge in the masterpiece Domain Driven Design, Tackling Complexity in the Heart of Software (DDD). I remember the debate and confusion on various blogs regarding entity vs. domain, which Frans put to a stop.
And today? I think there is still a lot of work to do (with .NET in mind). Microsoft is finally lending a hand in the sense of framework and tool support. Models are gaining interest in new technology stacks (MDA, DSL)… and finally we have a developer focused title to clamp on to while we bridge the gaps between PoEAA and DDD in code.