It's time to consider what is an aggregate and where an event belongs to. Is it always obvious where one belongs to?
DDD
Top Domain Model: I’m temporal
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 […]
Top Domain Model
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 … Continue reading Top Domain Model
Event stores and event sourcing: some not so practical disadvantages and problems
TL;DR This post is some kind of answer to the article mentioned in a tweet by Greg Young. The blog post of the author has no comment section. Also, this post contains a lot of information, so that's why I'm posting it instead of sending as an email or DM. Commits Typically, an event store … Continue reading Event stores and event sourcing: some not so practical disadvantages and problems
Event sourcing: making it functional (7)
TL;DR It's the seventh chapter of making event sourcing functional. In the last post we introduced the base class for aggregates capturing events and applying them on the state. In this entry we question this choice and make the final step to make our code more functional. Let's go! All entries in this series: 1 … Continue reading Event sourcing: making it functional (7)
Event sourcing: making it functional (6)
TL;DR In the last entry we changed the Payment aggregate to modify state by raising events. The events weren't captured though. In this post, we'll change the aggregate to enable recording of these changes. All entries in this series: 1 - back to foundations 2 - aggregate sketch 3 - first implementation 4 - finding … Continue reading Event sourcing: making it functional (6)
Event sourcing: making it functional (5)
TL;DR After defining events of the Payment aggregate it's time to move on and work on applying these events. All entries in this series: 1 - back to foundations 2 - aggregate sketch 3 - first implementation 4 - finding events 5 - applying events 6 - recording aggregate 7 - the fully functional end … Continue reading Event sourcing: making it functional (5)
