Every system has a story.
Event Sourcing keeps every change as it happened – in order, in the language of your domain. This is where you learn how it works, find the tools to build with it, and meet the people behind it.
Most systems know where they are. Not how they got there.
A typical database stores the current state and overwrites whatever came before. When someone asks what actually happened, why a value changed, or who decided what, the answer is no longer there.
- Jan 08book-acquired
- Feb 02book-borrowedreader 17
- Feb 23loan-extended+14 days
- Mar 23book-returned5 days late
- Mar 23late-fee-charged2.50 €
- current stateavailable
The reader borrowed the book. The book was returned late. A fee was charged.
In order
Events happen one after another. The sequence is part of the meaning, just like in a story.
Driven by verbs
Every event says what happened, in the words the people in your domain actually use.
In the past tense
Events are facts. They are never changed or deleted, only added. The history stays intact.
Five stages, one story.
Every stage has its concepts, explained without selling anything. Where we have built a tool for a stage, you will find it right next to them.
Model it.
Find the events that matter, together with the people who know the domain.
Remember it.
Store every change as a fact, and derive the current state from it.
Build on it.
Shape applications around the events, with clear boundaries and a functional core.
Learn from it.
Turn the history into insight, for people and for AI.
Start where you are.
For engineers
How does it work, and how do I build it?
- Concepts from modeling to learning
- Tutorials you can run today
- Docs for every product
For the business
What does it do for our domain?
- Events in the language of your business
- Workshops for modeling together
- Stories from real projects
For leadership
Is this a decision that holds?
- Audit and compliance by design
- An open specification, no lock-in
- Support and licensing
The database built for events.
Purpose-built for Event Sourcing: write, read, and observe events, with consistency guarantees and a tamper-evident history. From a Raspberry Pi to Kubernetes.
An open home for events.
Event Foundation is an initiative by the native web. It brings together concepts, open specifications, and the people who build with events – including partners and projects beyond our own.
Quickstart
This quickstart gets a first command running with ArchitectureKit in a few minutes: you start EventSourcingDB with Docker, define a command, an event, and the state to decide on, and execute the command. It uses a temporary setup for development and testing – for everything else, see the links at the end.
→Quickstart
This quickstart gets EventSourcingDB running on your machine in a few minutes: you start it with Docker, write a first event, and read it back. It uses a temporary setup for development and testing – for all other options, see the links at the end.
→First Steps with EventSourcingDB
This tutorial builds a small library step by step. You write events for books, read them back, query them with EventQL, observe them as they happen, register event schemas, generate sample data, and finally list the subjects and event types that EventSourcingDB knows about.
→