In the session we will go through the code for some of the DDD samples out there to see how they are put together structurally as well as discussing how they relate to the principals of DDD, how useful we think the principals are and even how effectively we think sample succeeds in illustrating DDD.
One sample has been suggested in http://code.google.com/p/ndddsample/ and I would also like to put forward this one https://github.com/MarkNijhof/Fohjin as another example that I believe uses event sourcing. The event sourcing sample is also backed by this blog post series http://cre8ivethought.com/blog/2009/11/12/cqrs--la-greg-young
(Interestingly both these samples are quite dated! I wonder why? Has anyone got any more up to date samples?)
(Interestingly both these samples are quite dated! I wonder why? Has anyone got any more up to date samples?)
I'll be interested to see what we come up with! As usual please indicate your intention to attend by voting on the right.
Wow, cool post. I'd like to write like this too - taking time and real hard work to make a great article... but I put things off too much and never seem to get started. Thanks though. Art prints posters
ReplyDeleteThe interactive code archaeology session offers an interesting way to examine Domain Driven Design samples by looking beyond theory and focusing on how real code is organized. Reviewing different implementations can help developers understand the structural choices made in sample projects while also considering how effectively those examples communicate the principles of DDD.
ReplyDeleteThe proposed samples provide an opportunity to compare different approaches to domain modeling, event sourcing, and related architectural concepts. Discussions around how useful these principles are in practice can also encourage developers to explore broader domains in computer engineering and identify suitable areas for practical project development.
Another valuable part of the session is the emphasis on evaluating whether a sample actually succeeds in illustrating the concepts it is intended to demonstrate. Looking at older examples and questioning the availability of newer implementations can help learners think critically about software architecture, technology choices, and evolving development practices within Domains in IT Industry.
ReplyDeleteOverall, the format of examining existing code, discussing DDD principles, and comparing different samples creates a useful collaborative learning experience. It encourages participants to connect architectural ideas with real implementations and explore potential areas for further study, including Domains in Computer Engineering when considering technology-focused project topics.
ReplyDelete