Ideas

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...

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...

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...

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...

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...

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...

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...

ESDB has an option to disabled automatic index merge, so users can do it manually. Usually, this option is enabled because automatic index merge can start at any time, and it might also get running on all the nodes at the same time. Since it's an ...

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 ...