
With all of these sample apps, it's probably best to check out the latest trunk versions from SVN/whatever to really get an idea of the thinking and technology patterns as they should be updated regularly. S#arp Architecture - a pragmatic C# example, not as "pure" a DDD approach perhaps due to its lack of a real domain problem, but still a nice clean approach. It's being actively worked on, so check it regularly for updates.ĭddps - Tim McCarthy's sample C# app for his book. These make up the tactics of Domain Driven Design. CQRS Event Sourcing and Domain Driven Design FAQ At Edument we enjoy helping teams apply Domain Driven Design often through Event Sourcing and CQRS Here weve collected resources that are Algorithm design - Wikipedia Algorithm design is a specific method to create a mathematical process in solving problems Applied algorithm design is algorithm.

Domain Driven Design, Where the real value lies. Evans - Domain-Driven Design CH15Distillation DDD. This is well commented and shows a number of different methods of solving various problems with separate bounded contexts (ie, the presentation layer). Mariusz.W on Twitter: 'Evans - Domain-Driven Design CH15 Mariusz.W MariuszWCrawley Jun 30. You haven't specified which language you're using, but I'll give you a few in a few different languages:ĭDDSample - a Java sample that reflects the examples Eric Evans talks about in his book. That said, a well commented sample app should at least reveal some of these decisions and give you some direction in terms of matching up your domain model with the technical patterns used to implement it.


(as some say, the best DDD sample is the book itself!) DDD is much more about the process than it is the code. The difficulty with DDD samples is that they're often very domain specific and the technical implementation of the resulting system doesn't always show the design decisions and transitions that were made in modelling the domain, which is really at the core of DDD.
