CategoryF#

Event Sourcing: Is our Projection Code fast enough?

E

In this part of my event sourcing series, we take a quick, pun intended, look at how fast the projector we saw in the last post actually runs. The projector gets a list of events as input and projects them into a single value, representing the latest state. This code runs a couple hundred times a second in our system, so it needs to run fast.

Event Sourcing: A close look at the projector for values

E

In this part of my event sourcing series, we look at implementing the projector for values (uni-temporal events / normal event sourcing). You’ll see the full source code for our ValueProjector, which projects events into a single value representing the latest state.

This brings together many of the things you’ve seen in earlier posts in this series.

Event Sourcing: fun with bi-temporal timelines

E

In earlier parts of this series on event sourcing, we have seen that we can project bi-temporal events (events with two timestamps: when the system knew about the event and when the event takes effect) into so-called timelines. A timeline shows a value over time. In this post, we look at some exemplary use cases these timelines enable.

Event Sourcing: two ways to enable accept/reject workflows

E

When an employee corrects the time they started or stopped working in a time-tracking system, a workflow typically notifies their manager or HR that the data has changed. Then, the manager or HR decides whether to accept or reject this change. The same goes for requests for vacation or other kinds of absences. There are two ways to solve this: First, with normal event sourcing and multiple event streams. Second, with dedicated accept and reject functionality in the projector. In this post...

Event Sourcing: Aggregates, Dynamic Consistency Boundaries, or what?

E

In part eleven of this series on event sourcing, we make a small detour to discuss consistency boundaries. I never thought much about this aspect until recently, when I watched a couple of conference talks that all made a big fuss about domain-driven design’s aggregates, and had a discussion with Sara Pellegrini about dynamic consistency boundaries. This post is less about the resulting solution we have and more about the reasoning that led to it (and that might lead to another solution...

Event Sourcing: the not-so-simple bi-temporal basics

E

It’s time for bi-temporal event sourcing in part eight of my event sourcing series. In this post, I’ll stick to the basics – at least I hope so. 😅 Bi-temporal event sourcing means that we have two timestamps associated with an event: The first timestamp tells us when the event entered the system, or when the system acquired the knowledge. We call this the application timestamp. The second timestamp states when the event takes effect – the effective timestamp. This is...

Recent Posts