Frequently asked questions (FAQs)

EventStoreDB is a new category of operational database that has evolved from the Event Sourcing community. Powered by an event-native data model, events are stored all the way down with the context of why they have happened. Providing flexible, real-time data insights in the language your business understands.

Download the newest version here .

Follow the getting started guide here.

Our community is also on hand to help you at every step of your journey.

Click here to view Event Store Ltd’s licensing information.

For guidance on installation, development, deployment, and administration, see the User Documentation.

You can find the latest versions of EventStoreDB on our downloads page.

This getting started guide shows you how to get started with EventStoreDB by setting up an instance or cluster and configuring it. EventStoreDB supports two protocols: gRPC and TCP(legacy).

EventStoreDB supported clients

• Go: EventStore/EventStore-Client-Go
• .NET: EventStore/EventStore-Client-Dotnet
• Java: (EventStore/EventStoreDB-Client-Java
• Node.js (javascript/typescript): EventStore/EventStore-Client-NodeJS
• Rust: EventStore/EventStoreDB-Client-Rust
• Read more in the gRPC clients documentation

Legacy TCP Clients

• .Net: EventStoreDB-Client-Dotnet-Legacy
• JVM: EventStore.JVM
• Haskell: EventStoreDB-Client-Haskell

Community developed clients

• Elixir: NFIBrokerage/spear
• Python: pyeventsourcing/esdbclient 
• Ruby: yousty/event_store_client

Read more in the documentation.

Follow our guide to get started with Event Store Cloud.

Follow these steps to host EventStoreDB yourself.

Our community is a space to learn more about EventStoreDB, the operational database that values data at its origin. Come discover why we are so much more than just another Event Store.

Development is done on the master branch. We attempt to do our best to ensure that the history remains clean and to do so, we generally ask contributors to squash their commits into a set or single logical commit.

If you want to switch to a particular release, you can check out the release branch for that particular release. For example:
git checkout release/oss-v22.10

• Create an issue
• Documentation
• Contributing guide

EventStoreDB is written in a mixture of C# and JavaScript. It can run on Windows, Linux and macOS (using Docker) using the .NET Core runtime.

Prerequisites

• .NET Core SDK 6.0

Once you've installed the prerequisites for your system, you can launch a Release build of EventStore as follows:

dotnet build -c Release src

The build scripts: build.sh and build.ps1 are also available for Linux and Windows respectively to simplify the build process.

To start a single node, you can then run:

dotnet ./src/EventStore.ClusterNode/bin/x64/Release/net6.0/EventStore.ClusterNode.dll --dev --db ./tmp/data --index ./tmp/index --log ./tmp/log

Running the tests

You can launch the tests as follows:

dotnet test src/EventStore.sln

Build EventStoreDB Docker image

You can also build a Docker image by running the command:

docker build --tag myeventstore . \
--build-arg CONTAINER_RUNTIME={container-runtime}
--build-arg RUNTIME={runtime}

For instance:

docker build --tag myeventstore . \
--build-arg CONTAINER_RUNTIME=bullseye-slim \
--build-arg RUNTIME=linux-x64

Note: Because of the Docker issue, if you're building a Docker image on Windows, you may need to set the DOCKER_BUILDKIT=0 environment variable. For instance, running in PowerShell:

$env:DOCKER_BUILDKIT=0; docker build --tag myeventstore . `
--build-arg CONTAINER_RUNTIME=bullseye-slim `
--build-arg RUNTIME=linux-x64

Currently we support following configurations:

1. Bullseye slim:

• CONTAINER_RUNTIME=bullseye-slim
• RUNTIME=linux-x64

2. Focal:

• CONTAINER_RUNTIME=focal
• RUNTIME=linux-x64

3. Alpine:

• CONTAINER_RUNTIME=alpine
• RUNTIME=alpine-x64

You can verify the built image by running:

docker run --rm myeventstore --insecure --what-if

We offer plans for every stage of project from proof of concept to successful operation in production, with a range of SLAs to suit startups to enterprise organizations worldwide. You can view more here.

We offer public and private training for Event Sourcing, CQRS, DDD, and EventStoreDB with our professional training courses for developers and software architects. You can view more information here.

• Release notes
• Beginners Guide to Event Sourcing
• Articles
• Webinars
• Contact us

Event Store Cloud is a fully managed cloud offering that’s designed to make it easy for developers to build and run highly available and secure applications that incorporate EventStoreDB without having to worry about managing the underlying infrastructure. You can provision EventStoreDB clusters in AWS, Azure, and GCP, and connect these services securely to your own cloud resources.

Follow our guide to get started with Event Store Cloud. 

You can find our Event Store Cloud documentation here.

With your account, you might have more than one organisation. Each organisation has its own billing account and therefore is invoiced separately for all the resources within the organisation. For example, if you have several customers and want to have a separate EventStoreDB cluster for each customer and also be able to bill the customer for the cloud resources, you can separate each customer into its own organisation.

Event Store Cloud allows you to provision EventStoreDB clusters in AWS, GCP, and Azure.

The provisioning process consists of the following steps:

1. Create a network in Event Store Cloud.
2. Peer the new network with your own network at the same cloud.
3. Deploy the EventStoreDB cluster.

Find the detailed guideline for your cloud provider:

• Amazon Web Services (AWS)
• Google Cloud Platform (GCP)
• Microsoft Azure

Use this guide to assess the needs of your application performance, compared with the capability of a given EventStoreDB instance in Event Store Cloud.

When replacing a self-hosted EventStoreDB cluster with the managed cluster in Event Store Cloud, you might need to migrate the data, so your workloads can switch to the cloud cluster.

Currently, the only way to migrate data to the cloud cluster or instance is live migration by replication. Live migration is done by reading events from the source database (from $all) using a client protocol (TCP or gRPC) and then writing those events to the target database

Follow our guide here.

We don't have this feature available yet. However, you can always do it using backup and restore.

You will be able to do an online instance resize, but it won't be auto-scaling. You will have to change the instance size for your clusters yourself, when this feature will become available.

The Event Store Cloud roadmap is available on our website, scroll down to see the roadmap.

No, you have to resize the disks yourself. Disks can be expanded on-demand in AWS and GCP. For Azure read the procedure in the documentation. Because cloud providers limit how often disk resize operations can be performed the EventStore Cloud may enforce a waiting period on recently resized clusters before they can get resized again.

We published such benchmarks available on the Cloud instance sizing guide page.

Please remember, however, that each use case is different, and you might always get better or worse performance, compared with our advertised benchmarking figures. We can help you to analyse your needs and provide more detailed expected performance figures, please get in touch.

Yes. Learn more in the Events Console documentation section.

Event Store Cloud site reliability engineering (SRE) team manages cluster availability.

Please ensure to learn about the SLA levels provided by Event Store Cloud in our Service Level Agreement.

The list of supported regions is in the provisioning documentation.

At the moment, you can deploy EventStoreDB clusters only in regions with three or more availability zones. Each region also need to support a set of services necessary for the provisioning and monitoring of the clusters.

If you think a region should be available contact us.

Yes. Go to the clusters list in the Cloud Console, select the cluster you need and click on the Addresses tab on the bottom panel. You will find the admin UI URL there. You need to be connected to a network, which is routed to Event Store Cloud to open the admin UI in your browser.

Yes, we are actively working on it.

The scheduled backup feature has been released in March 2021. Read more in cloud backup documentation.

We plan to allow backup copies to the customer cloud account in the future. Currently, it's not possible because of security considerations.

You can find out about the SLA levels provided by Event Store Cloud in our Service Level Agreement.

All Cloud customers can choose to add commercial support covering core EventStoreDB usage and version upgrade support. Choose from a range of SLAs to suit your project requirements. You can find out more here.

Event Store Ltd has security policies in place. You can find out more here.

If you have specific questions please contact us.

Event Store Ltd is aware of the security importance. We're treating it is as a high priority. Our Cloud offering has been independently audited, and we achieved SOC 2 and ISO 27001 certification in January 2022.

If you have specific questions please contact us.

You can view our pricing here.

• Release notes
• Beginners Guide to Event Sourcing
• Articles
• Webinars
• Contact us