wtf is kurrentdb?

KurrentDB is a database built specifically for event-driven software architectures. Rather than storing only the latest state of your data (as a typical relational database does), KurrentDB records every change as an ordered sequence of events. This design pattern, often called event sourcing, makes it straightforward to reconstruct the full history of what happened in your application, audit past states, or replay events to rebuild data in a new format. The project was previously called EventStoreDB, published by a company called Event Store. That company has rebranded to Kurrent, and the product has been renamed KurrentDB accordingly. The underlying software is the same, only the name changed. KurrentDB includes a streaming engine that handles messaging between parts of a distributed system. Instead of bolting on a separate message queue, the database itself can push new events to subscribers as they are written. This means an application can both persist events and react to them in near real time without needing an external broker. The database is written in C# and JavaScript, runs on Windows, Linux, and macOS, and communicates with client applications over the gRPC protocol. Official client libraries are available for Python, Node.js, Java.NET, Go, and Rust. Community-maintained clients exist for Elixir and Ruby as well. You can run KurrentDB yourself by building from source or using the provided Docker image. Alternatively, Kurrent offers a managed cloud service called Kurrent Cloud, which provisions and operates KurrentDB clusters on AWS, Azure, or Google Cloud on your behalf. The cloud option is aimed at teams that want the capabilities of the database without managing the infrastructure.