What does it do for our domain?
Events speak the language of your business. They are found together with the people who know the domain, and they keep a history you can learn from later.
Speak the language of your domain
Events describe what happens in your business, in its own words. Domain-Driven Design and Event-Storming find them together with the people who know the domain.
Domain-driven design (DDD) is an approach to software design that puts the business domain at the center of the system.
Event-StormingThis guide introduces Event-Storming as a collaborative modeling technique for discovering and designing events in event-sourced systems.
Modeling EventsThis guide explains how to model events effectively in an event-sourced system.
Write the model down
A domain model as files next to the code, checked by a linter and reviewed like any other change.
Learn from what happened
Since every event is kept, you can answer questions later that nobody asked when the system was built.
This guide explains why an event-sourced history is the best raw material for analytics, machine learning, and AI, and how the path from events to insights is structured.
Patterns for Temporal QueriesThis guide explores patterns for performing time-based queries in event-sourced systems.
Posts on analyzing eventsThe blog, on what events tell you long after they happened.
Work with us
Workshops for modeling your domain together, training, and consulting.