Skip to Main Content
EventStoreDB Ideas Portal

Ideas for improvements and new features in EventStoreDB, client libraries, and database extensions.

ADD A NEW IDEA

Ideas

Showing 21 of 56

Read only start up mode

Have to ability to start a single node EventStore in complete read-only mode. This will allow the rebuilding of corrupted indexes on a different server from a production backup without worrying about surpassing the production checkpoint due to new...
Guest over 1 year ago in EventStoreDB / Dev experience 3

Support authorisation when reading from $all

Currently, reads and subscriptions to $all require admin access, which isn't good for security. Supporting auth for $all will have performance impact when ACLs are used, but in combination with policies it could be fast enoguh because policies, un...
Alexey Zimarev almost 2 years ago in EventStoreDB / Dev experience / Security 0 Planned

Stream authorisation policies

ESDB has access control lists (ACLs) as the primary method to achieve granular (per stream) authorisation. However, ACLs need to be set up per stream, which is a burden for developers. Also, if the auth rules change, all the streams need to get th...
Alexey Zimarev almost 2 years ago in EventStoreDB / Dev experience / Security 0 Planned

Chunk format optimised for reading

The idea is to rewrite the chunk file after it stops accepting writes, so it can handle reads better. Re-sort events in closed chunks to group events of the same stream together for efficient IOPS use. Could also save having to repeat the stream n...
Tim Coleman almost 2 years ago in EventStoreDB / Performance 0

Add catchup subscription stats to HTTP API

No description provided
Alexey Zimarev almost 2 years ago in EventStoreDB / Dev experience / Operations 0 Planned

Event metadata format

Leverage map style metadata, used in cloud events that propagate as HTTP/message headers. Having event metadata as JSON sounded like a good idea at a time, but it creates a lot of friction when things need to be retrieved or added, like tracing he...
Alexey Zimarev almost 2 years ago in EventStoreDB / Dev experience 0

Multiple databases

Allow having multiple logs (databases) physically separated from each other. That would include different set of users, authorisation rules, etc. It would enable: deleting a specific database instead of cleaning up the whole cluster separate data ...
Alexey Zimarev almost 2 years ago in EventStoreDB / Dev experience / Operations / Security 0 Planned

SLA for Reads

When reading from followers, allow setting time SLA for the read operation to ensure you get fresh enough data. It helps offloading the read load without imposing too much risk of reading very stale data.
Alexey Zimarev almost 2 years ago in EventStoreDB / Dev experience 0 Planned

Tiered Storage and Archive

Introduction In today's data-driven world, the storage and management of events play a crucial role in various industries. However, storing all events indefinitely can be both space-intensive and costly. To address this challenge, we propose the i...
Alexey Zimarev almost 2 years ago in EventStoreDB / Operations / Performance 0

Server-side snapshots

Stream snapshots is one of the commonly used techniques to improve performance when reading long streams. Currently, developers are required to build snapshotting on their own, although it's quite clear how to do it. ESDB can support server-side s...
Alexey Zimarev almost 2 years ago in EventStoreDB / Dev experience 0