In event-sourced systems, the domain model is using events as the source of truth. These events represent individual and atomic state transitions of the system. We add events to the event store one by one, in an append-only fashion. When restoring the state of an aggregate, we read all the…

What is Eventuous Connector and how to use it Eventuous connectors allow subscribing to events from EventStoreDB (source) and produce derived events to another system (sink). Some sinks also support reduce-like operations that work as projections. The Connector is a combination of a real-time subscription (currently only to $all stream)…

Real-time subscriptions are essential when building a successful event-sourced system. They support the following sequence of operations: The domain model emits a new event The event is stored in the event store The command is now handled, and the transaction is complete All the read models get the new event…

I wrote a page about domain events for Eventuous documentation today. It landed as a blog article, so I decided to publish it separately as such. Concept If you ever read the Blue Book, you’d notice that the Domain Event concept is not mentioned there. Still, years after the book was…