Mission
Every system has a story, but most systems keep only its last page: what is true right now, not how it came to be. What gets lost are the answers to questions nobody has asked yet – why something happened, what was known at the time, and what can be learned from it.
Events keep the whole story. Working with them well is a craft of its own, from modeling a domain to learning from its history, and what there is to know about it is scattered across books, talks, blogs, and products that each tell a part. The Event Foundation brings it together in one place.
What we do#
- Explain. Concepts describes the ideas behind event-based systems, from Domain-Driven Design to Event-Driven Architecture, along the five stages of their lifecycle.
- Teach. Learn leads step by step from the first event to a running system.
- Document. Docs is one portal for the documentation of our products.
- Collect. Resources gathers articles, papers, and talks.
- Map. The Landscape shows the products of the ecosystem, ours and those of others.
- Specify. We maintain open specifications, starting with ESDM, a format for event-sourced domain models.
What we stand for#
- Concepts come without products. They explain ideas, not tools. Where a product helps to try something out, a marked box says so.
- The Landscape selects, but does not rate. Our own products are listed by the same rules as everyone else's, without a preferred place, and no one pays to be listed.
- Specifications are open. Anyone can use and implement them.
Who is behind it#
The Event Foundation is an initiative by the native web GmbH, not a legal entity of its own. We also build products for event-based systems, such as EventSourcingDB, and we sell them – openly, under Products, and kept apart from everything else by the principles above.