So, back when I started out after my studies in 2003, a new book came up by Eric Evans which took all the Martin Fowlers and Gang of Fours and all other hearts by storm, ordering the next level of design thinking to software into a brand name and into something you could almost call a methodology.
Focus on the domain, make your domain model the strong factor, have a common language to talk about it, take these patterns and principles as standard mapping.
- Focus on the core domain and its logic instead of modeling getter/setter nightmares with actionscript-services.
- Have a complex domain modeled properly
- Synchronize understanding and findings continuously with the domain experts
Of course I was trying to get the Pluralsight-Expertranking-Skillcheck as kind of a freebie, as I was writing software in an environment that adhered strongly to this church from 2003 to 2010. Haha. okay, I failed the expert ranking on the first try. So…. something must have changed drastically in the field, right? Nah. But, the scope if you talk with people about Domain Driven Design was broadened.
EVENT SOURCING is now a part of DDD, at least on Pluralsight. Haha. Okay. So Event Sourcing is the idea to not store final state but to store processes and changes which are leading to the current state of the system. you could replay the events, you could audit on the events, etc. Is it core DDD? I really don’t think so.
CQRS Command and Query Responsibility Segregation is now a part of DDD for Pluralsight, too. Hm. ooohkay. Have a complex model for modification of the data, speed ahead on retrieval, I get that.
In my understanding these are really independent concepts that work in categories of their own. But with Pluralsight mashing these together and then only offering videocourses in C#, I was in for a treat and actually learned some new stuff this way, including database contexts in C# which I hopefully never need to use 😉
Finished the Skillcheck with an Expert Rating. Still got two of the C# questions wrong. Decided not to care.