How does it work, and how do I build it?
From the ideas behind Event Sourcing, CQRS, and Domain-Driven Design to a running application – and the tools to build it with.
Understand the concepts
The ideas behind it all, explained without any product – what an event is, why you keep every one of them, and how commands, events, and read models fit together.
This guide introduces the concept of event sourcing and explains how it differs from traditional approaches to storing application state.
What is CQRS?CQRS stands for Command Query Responsibility Segregation.
What is Domain-Driven Design?Domain-driven design (DDD) is an approach to software design that puts the business domain at the center of the system.
Run it yourself
Write your first events, read them back, query them, and observe them as they happen, step by step.
Build an application
Decide on commands, write events, keep read models up to date, and test all of it.
This tutorial builds a small library in Go step by step.
Building Event-Driven ApplicationsThis guide explains how to design and implement event-driven applications on top of an event store.
Testing Event-Sourced SystemsThis guide explains how to test event-sourced systems.
Look it up
The documentation of our products, from the quickstart to the reference.
Pick your tools
Our products along the lifecycle, and the landscape of what others build around Event Sourcing.