EventStoreDB

Showing 41 of 57

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 over 1 year 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 over 1 year ago in EventStoreDB / Dev experience / Security 0 Planned

2 VOTE

Backup and restore

Implement backup and restore as database functions.

Alexey Zimarev over 1 year ago in EventStoreDB / Operations 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 over 1 year ago in EventStoreDB / Operations / Stability 0 Planned

4 VOTE

Filtered reads and subscriptions to streams

ESDB currently allows filtered subscriptions to $all. The idea is to support filtered reads from $all, from streams, as well as filtered catch-up subscriptions to streams.

Alexey Zimarev over 1 year ago in EventStoreDB / Dev experience 2

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 over 1 year ago in EventStoreDB / Dev experience / Performance / Stability 0

3 VOTE

Projections next-gen

Move custom and standard projections to Connectors.

Alexey Zimarev over 1 year ago in EventStoreDB / Performance / 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 over 1 year ago in EventStoreDB / Dev experience / Security 0 Planned

1 VOTE

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 over 1 year ago in EventStoreDB / Operations / Stability 0

7 VOTE

Delete streams without a trace

Customers who actively clean up their database encounter a situation when the scavenge.db file grows uncontrollably because it keeps the information about stuff that has been deleted. Eventually, it might lead to a situation when the scavenge.db f...

Alexey Zimarev over 1 year ago in EventStoreDB / Operations 3

Please enter your email address

FILTER BY CATEGORY