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 14 of 56

Schema registry

Have a component that would allow developers to register their events schema in the registry. When appending new events, when the schema id is provided, the event is checked for compatibility with the schema, and it it's not compatible, the append...
Alexey Zimarev almost 2 years ago in Platform / Schema 0

Chained replicas

Current implementation of read-only replicas require them to be connected to the cluster. It means that every new replica adds some overhead to the operational cluster nodes, particularly its leader. It creates limitation of the feature as one mig...
Alexey Zimarev about 1 year ago in EventStoreDB / Performance / Stability 0

Projections next-gen

Move custom and standard projections to Connectors.
Alexey Zimarev almost 2 years ago in EventStoreDB / Performance / Stability 0 Planned

Support certificates with EC (elliptic curve) keys

ESDB currently supports only RSA keys in certificates when specifying --certificate-private-key-file. The advantage of using EC keys would be that the key is much smaller for the same security level (EC takes 256 bit vs RSA 2048 bit for same secur...
Alexey Zimarev over 1 year ago in EventStoreDB / Configuration / Operations / Security 1

Persistent subscriptions next-gen

Seems like persistent subscriptions aim to solve two problems: Server-side checkpointing for use cases when events are being forwarded to a place that doesn't have the ability to store checkpoints (message brokers), or users just don't want to dea...
Alexey Zimarev almost 2 years ago in EventStoreDB / Dev experience / Performance / Stability 0

Crypto-assurance for audit

Crypto-assurance provides guarantees against mutations, truncation, and reordering. Although ESDB doesn't provide nativa mutation and reordering capability, data on disk can be tampered to change the content of events. ESDB supports truncation wit...
Alexey Zimarev over 1 year ago in EventStoreDB / Compliance / Security 0

Store some configuration in the database

ESDB is primarily configured using the config file, which is located on each cluster node. Some features (projections, connectors) are configured in the database itself. It can be confusing to understand where things are configured and why some co...
Alexey Zimarev almost 2 years ago in EventStoreDB / Configuration / Operations 0 Planned

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

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 almost 2 years 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 almost 2 years ago in EventStoreDB / Dev experience / Security 0 Planned