Welcome to the EventStoreDB documentation.
EventStoreDB is a database designed for Event Sourcing. This documentation introduces key concepts of EventStoreDB and explains its installation, configuration, and operational concerns.
EventStoreDB is available in both an Open-Source and a Commercial version:
- EventStoreDB OSS is the open-source and free-to-use edition of EventStoreDB.
- EventStoreDB Commercial is available for customers with an EventStoreDB paid support subscription. EventStoreDB Commercial adds enterprise-focused features such as LDAP and X.509 authentication, OpenTelemetry Exporter, correlation event sequence visualisation, and management CLI tool.
Find out what's new in this release to get details on new features and other changes.
Check the installation guide for database setup and first-run guidance.
Users of EventStoreDB OSS can use the community forum for questions, discussions and getting help from community members.
Customers with the paid support plan can open tickets using the support portal.
Since EventStoreDB is an open-source product, we track most of the issues openly in the EventStoreDB repository on GitHub. Before opening an issue, please ensure that a similar issue hasn't been opened already. Also, try searching closed issues that might contain a solution or workaround for your problem.
When opening an issue, follow our guidelines for bug reports and feature requests. By doing so, you will greatly help us to solve your concerns most efficiently.
EventStoreDB supports one client protocol, which is described below. The older TCP client API has been deprecated in version 20.2 and removed in version 24.2. The final version with TCP API support is 23.10. More information can be found in our blog post.
Since version 24.6, the legacy protocol is available as a commercial plugin available for Event Store customers.
The client protocol is based on open standards and is widely supported by many programming languages. EventStoreDB uses gRPC to communicate between the cluster nodes as well as for client-server communication.
When developing software that uses EventStoreDB, we recommend using one of the official SDKs.
- Python: pyeventsourcing/esdbclient
- Node.js (JavaScript/TypeScript): EventStore/EventStore-Client-NodeJS
- Java: EventStore/EventStoreDB-Client-Java
- .NET: EventStore/EventStore-Client-Dotnet
- Go: EventStore/EventStore-Client-Go
- Rust: EventStore/EventStoreDB-Client-Rust
Use the official SDK documentation for language-specific gRPC client guidance.
EventStoreDB also offers HTTP surfaces for the Admin UI, management workflows, health probes, gossip, and diagnostics. Application event access uses the gRPC clients listed above.
Find out more about configuring the HTTP protocol on the HTTP configuration page.