It's snapshot time! There's been a lot of event sourcing content so far. Let's do a recap! Below you will find a short summary of event sourcing related articles that I have published here so far. Treat it as a table of content or a lookup or a pattern collection. It's ordered by date, the … Continue reading Snapshot time!
TL;DR Do you know that feeling of being powerless? Of being not able to tell why your system acted in a specific way? Of not being able to recognize whether it's a hacker or your system malfunction? Event sourcing, by storing all the events that happened in your system helps a lot. Still, you can … Continue reading Why did it happen?
TL;DR When modelling with event sourcing, people often tend to create long living streams/aggregates. I encourage you to improve your modelling with interim streams. Long live the king A user, an account, a company. Frequently this kinds of aggregates are distinguished during first modelling attempts. They are long lasting, never ending streams of events. Sometimes … Continue reading Event Sourcing and interim streams
Recently I've been revisiting some of my Domain Driven Design, CQRS & Event Sourcing knowledge and techniques. I've supported creation of systems with these approaches, hence, I could revisit the experiences I had as well. If you are not familiar with these topics, a good started could be my Feed Your Head list. Inside So … Continue reading Events on the Outside versus Events on the Inside
When considering the application of event sourcing it's quite common to allow a common part for all the events, the metadata. Various stores handle it in separate but common ways. EventStore lets you append the metadata with events. The same you can do with NEventStore using headers. But what information can be useful to store … Continue reading Enriching your events with important metadata