A browser-based application for Domain-Driven Design, from Event Storming and Domain Storytelling to a model that exports to ESDM.
- License
- Proprietary
- Runs on
- Container
The products around Event Sourcing, CQRS, and Domain-Driven Design, ours included – all in the same form, along the five stages, and described without evaluation.
A browser-based application for Domain-Driven Design, from Event Storming and Domain Storytelling to a model that exports to ESDM.
A command-line tool that checks, explores, and documents event-sourced domain models written in ESDM.
A web application for visually browsing domain models written in ESDM.
A service that generates realistic, synthetic events of sample domains, to explore event-sourced data and to build on it.
A server that provides message routing and an event store for message-driven applications.
A purpose-built database for Event Sourcing.
Continuous chain verification and external fingerprint custody for EventSourcingDB.
A database for event-driven architectures with an integrated streaming engine.
Building blocks for DDD-based applications with CQRS and Event Sourcing in Go.
A framework for building applications following CQRS and Event Sourcing in Elixir.
An event store adapter that integrates Commanded with EventSourcingDB.
A lightweight CQRS and Event Sourcing framework for Rust, targeting serverless architectures.
An EventSourcingDB implementation of the event repository of cqrs-es.
A framework for building event-driven applications in TypeScript, with commands, queries, and events following CloudEvents.
A framework for building CQRS and Event Sourcing applications on the JVM, with optional Spring Boot integration.
Live analyses and dashboards, inferred from the events of an EventSourcingDB.
No entries match these filters.
Everything listed has to do with Event Sourcing, CQRS, or Domain-Driven Design; general technology, such as a general-purpose database or message broker, is not listed. An entry is listed if it is one of our products, or builds on one of them with a value of its own; if it bridges one of our products and another product of the ecosystem; if it is the other side of such a bridge; or if we consider it worth mentioning for a reason of our own. What only simplifies access to a product, such as a client SDK, is part of that product and listed in its documentation.
We choose what is listed, but we do not evaluate what we list.