Skip to Main Content
EventStoreDB Ideas Portal

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

ADD A NEW IDEA

EventStoreDB

Showing 46 of 57

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 8 months ago in EventStoreDB / Dev experience / Security 0 Planned

Policy-based authorisation

ACLs are hard to manage because they are stream specific. Adding poicies that would cover things like category would make authorisation a lot easier to set up.
Alexey Zimarev 8 months ago in EventStoreDB / Dev experience / Operations / Security 0 Planned

Handle backpressure

ESDB can be overloaded with read/write operations and it has no limitations enforced on the edge to prevent this. The idea is to set the connection limit (in general or per operation) and deny requests when the limit is exceeded. It will improve t...
Alexey Zimarev 8 months ago in EventStoreDB / Operations / Stability 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 8 months ago in EventStoreDB / Dev experience / Security 0 Planned

Replication between clusters

Allow one cluster to mirror another. Could be similar to read-only replica, but instead of a single node that is known to the source cluster, the mirror would be a read-only replicated cluster. One use of it is to enable faster reads. If the "oper...
Alexey Zimarev 8 months ago in EventStoreDB / Operations / Stability 0

Custom Indexes

Focus on removing linkto eventsIncludes sequence numbers$allcategoryguarantees on write (optional consistency) from a client perspective also defined by user?
Alexey Zimarev 8 months ago in EventStoreDB / Dev experience 1

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 8 months ago in EventStoreDB / Performance 0

Automated Scavenging

Scavenging is a routine maintenance operation in ESDB, but it requires DB admins to run it either manually or using some automation like curl call to the DB API executed by cron. It's not only inconvinient, but also isn't optimal as scavenging nor...
Alexey Zimarev 8 months ago in EventStoreDB / Operations / Stability 0 Planned

Add catchup subscription stats to HTTP API

No description provided
Alexey Zimarev 8 months 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 8 months ago in EventStoreDB / Dev experience 0