Skip to content

EventSourcingDB

EventSourcingDB is a database purpose-built for event sourcing, developed and maintained by the German company the native web GmbH.

Unlike general-purpose databases or streaming systems that can be adapted for event storage, EventSourcingDB was designed from the ground up to address the core requirements of event sourcing. Its focus lies on simplicity of setup, adherence to open standards, and direct support for common event sourcing patterns such as writing, reading, and observing events.

The product is closed source but available under a tiered license: up to 25,000 events can be stored free of charge, making it suitable for evaluation, development, and typical test scenarios. Beyond that threshold, a commercial license is required. In addition, a managed cloud offering is available in a private beta, and additional support plans can be purchased for enterprise adoption.

Noticed Inaccurate or Outdated Information?

Despite our best efforts to keep this information accurate and up to date, details may change over time. If you find information that is inaccurate or outdated, please let us know so we can correct it quickly. You can reach us anytime at hello@thenativeweb.io.

Core Strengths and Focus Areas

EventSourcingDB emphasizes a design philosophy that balances simplicity for common use cases with sufficient flexibility for advanced scenarios. This is reflected in several core aspects:

  • Simplicity of Deployment: Distributed as a single statically linked binary, EventSourcingDB runs without external dependencies. It supports macOS, Linux, and Windows, on both x86 and ARM. For containerized setups, an official Docker image is available, and Kubernetes deployments are supported. This approach follows cloud-native principles but remains lightweight for on-premise use.

  • Standardized Interfaces: All functionality is exposed via a simple HTTP API, reducing integration friction. The database uses the CloudEvents standard as its event format, ensuring interoperability and familiarity for teams that already work with event-driven systems.

  • Core Operations: At its heart, EventSourcingDB is built around three primary operations:

    • Writing events in an append-only way, with atomic handling of multiple events and optimistic locking support.
    • Reading events, either for a single subject or recursively for entire hierarchies.
    • Observing events, combining replay of history with real-time subscriptions, effectively covering transactional outbox patterns without additional infrastructure.

  • Integrity and Auditability: Events are cryptographically linked through predecessor hashes, creating a blockchain-like chain that makes tampering detectable. An audit endpoint allows external systems to verify that the event log remains consistent over time. Optional digital signatures further strengthen authenticity guarantees for compliance-sensitive environments.

  • EventQL: Beyond subject-based reads, EventSourcingDB provides an expressive query language designed for ad-hoc exploration. EventQL supports filtering, grouping, aggregation, and subqueries, enabling users to ask complex questions without creating permanent projections. While powerful, EventQL is intended for exploratory queries rather than high-frequency read models, where subject-based reads perform more efficiently.

  • Observability and Integration: The system integrates with standard monitoring and tracing tools through Prometheus-compatible endpoints and OpenTelemetry support. A built-in management UI provides visibility into health and operational state. Client SDKs are officially maintained for multiple languages and ecosystems, including .NET, Go, Java, JavaScript/TypeScript, PHP, Python, and Rust, all with Testcontainers support for automated testing.

Challenges and Trade-offs

Despite its strengths, EventSourcingDB is still evolving and comes with a few trade-offs:

  • Authorization Model: Currently, access control is limited to a single API token. Fine-grained authorization with role-based access control is planned for future releases but not yet available.

  • Clustering: The database currently operates as a single instance. Horizontal scaling and clustering are on the roadmap but not part of the current feature set.

  • GDPR Support: Data protection and GDPR compliance are primarily the responsibility of applications built on top of EventSourcingDB. Improved first-class support for compliance features is planned for upcoming releases.

  • Projections: EventSourcingDB deliberately does not provide integrated projections. The design principle is to keep the database focused on storing and serving events, leaving projections to application-level code or external services. This differs from some other event stores, which embed projection capabilities.

These points are important to consider when evaluating whether the product fits a particular organization's requirements. In many cases, they represent conscious trade-offs rather than technical gaps.

Resources and Ecosystem

While EventSourcingDB does not bundle an application framework, it is often used in combination with external tooling. A notable example is OpenCQRS, an application framework for the JVM that is designed to work on top of EventSourcingDB, providing higher-level abstractions.

Further information is available through the official documentation, which includes detailed guides for installation, running the database, writing and reading events, query capabilities, and operations. The vendor also provides direct support channels for commercial customers.

Summary

EventSourcingDB positions itself as a modern, cloud-native, and lightweight event store.

Its guiding principle is to keep simple scenarios approachable while enabling advanced use cases through features such as EventQL, audit chains, and digital signatures. By emphasizing standards, simplicity, and interoperability, it lowers the barrier to entry for teams experimenting with event sourcing while remaining relevant for enterprise deployments that demand compliance and integration with existing technology stacks.

At the same time, its single-instance architecture and current authorization model highlight areas where functionality is still maturing. Organizations evaluating EventSourcingDB should weigh its ease of use and standards-based design against current limitations in scalability and access control.

Further Resources

For more details on EventSourcingDB, see: