Frequently asked questions (FAQs)

Kurrent 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 Kurrent on our downloads page.

This getting started guide shows you how to get started with Kurrent by setting up an instance or cluster and configuring it. Kurrent 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 Kurrent Cloud.

Follow these steps to host Kurrent yourself.

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

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 Kurrent 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 Kurrent 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

Kurrent 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 Kurrent Cloud. 

You can find our Kurrent Cloud documentation here.

Yes, you can have as many organizations as you need. Please note that each organization will be billed separately.

See our Getting Started guide here.

Every organization has its own individual AWS account, GCP project and Azure subscription.

Please use this guide. If you have any questions, please contact us through the Support button in the Kurrent Cloud Console.

Please follow this guide to migrate your data.

Please follow our guide here.

Yes, a cluster’s instance size can be increased by following these steps. On a three-node cluster this will be a rolling upgrade which ensures zero downtime.

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

Automatic resizing of cluster nodes is currently on the Kurrent Cloud roadmap.

No, automatic disk resizing is currently not available. Disks can be expanded manually using the procedure in the documentation.

If you wish to automate cluster resizing, the esc command line tool, as well as the Terraform and Pulumi providers are options to consider.

Because cloud providers limit how often disk resize operations can be performed the Kurrent Cloud may enforce a waiting period on recently resized clusters before they can get resized again.

Yes. We currently integrate with OpsGenie and Slack. Learn more in the Events Console documentation section.

How do you handle infrastructure related issues, which cause unavailability or degradation of service?

You can see the list of supported regions when you create a new cluster in the Cloud Console.

If you think a region should be available please 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, scheduled scavenge will be released in EventStoreDB version 24.10, which will be available on Event Store Cloud.

Yes, backups can be scheduled to run automatically. Please see the documentation here.

To obtain a copy of your data, please contact support using the button in the Cloud Console UI.

The ability to download backups directly from the UI  is on our roadmap.

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

Yes,. Please click here to find out more.

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