This is the end of mini series related to Top Domain Model. Let's quickly go through all the topics we've covered.

Make things implicit (more) explicit. This is the mantra we often here, but when touching the reality of software development, often forget, because of the magic beauty of technology, tooling, etc. Should we repeat this, when modelling domains as well?

Is it possible to stick just to aggregates to model your domain? Is it possible to make it any better with services or maybe another tool is needed?

In this episode, we will revisit this idea by referring to the good old-fashioned Twitter and its timelines. How timelines are created? Is everyone treated equally? Is it only aggregates' identities that should be pivoted or maybe our thinking as well?

It's time to consider what is an aggregate and where an event belongs to. Is it always obvious where one belongs to?

It looks like a new series is going to be published on this blog! I received some feedback related to the recent series making your event sourcing functional. Posts in this series will be loosely coupled and more-less self-contained. The topic that will connect them is modelling your domain, aggregates, processes towards models that are […]