Risk: à la Domain Driven Design

Ok, attempt two A few weeks back I decided I was going to use my new found DDD approaches, combined with CQRS and ES, to design the game Risk. And, completely counter to what the practices teach, I went off and started coding a solution with minimal thought or planning. I quickly decided on aggregates and boundaries and off I went, writing my first blog post explaining my proposed solution. By the way, I mentioned this as well in my first blog post. I'm not really going to go into much detail on the principles of DDD/ES/CQRS but…

Read More

Entities should look after their own events

I've been playing with CQRS and ES a lot recently and to be fair I should have started blogging about my experiences before now. But better late than never. This week I've been looking more carefully at how to manage the events that get applied to an entity within my aggregate root. When you first start your journery into CQRS/DDD/ES it won't be long before you come across the term aggregate. To quote Martin Fowler: A DDD aggregate is a cluster of domain objects that can be treated as a single unit. An example may be an order…

Read More