All ideas

Showing 53 of 53

Backup and restore

Implement backup and restore as database functions.

Alexey Zimarev 10 months ago in EventStoreDB / Operations 0 Planned

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 5 months ago in EventStoreDB / Dev experience 3

2 VOTE

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 11 months ago in EventStoreDB / Dev experience / Performance / Stability 0

2 VOTE

Support running ESDB on ARM64 Linux distributions

Substantial population of developers use Apple computers with ARM chip, and they currently cannot run ESDB locally even in Docker. We do have an "alpha" image but nobody gives any guarantees that everything works there. By providing a supported im...

Alexey Zimarev 11 months ago in EventStoreDB / Dev experience / Operations 0 Planned

1 VOTE

Make the scavenge.db file take up less space

At the moment it has to detect and track stream hash collisions, but it would be possible to track these more easily in the database itself (without taking additional space) and remove the significant bulk of scavenge.db. It may also make the accu...

Tim Coleman 7 months ago in EventStoreDB / Operations 0

1 VOTE

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 10 months ago in EventStoreDB / Compliance / Security 0

1 VOTE

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 10 months ago in EventStoreDB / Configuration / Operations 0 Planned

1 VOTE

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

1 VOTE

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 11 months ago in EventStoreDB / Operations / Stability 0 Planned

1 VOTE

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

Please enter your email address

FILTER BY CATEGORY