Ideas

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

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

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

Introduction In today's data-driven world, the storage and management of events play a crucial role in various industries. However, storing all events indefinitely can be both space-intensive and costly. To address this challenge, we propose the i...

Allow clients to control write guarantees. Right now, ESDB confirms the write when the leader has flushed data to disk, and the majority has the data in memory. Possible additional options: All followers have data in memory so they can do consiste...

Changing the database configuration currently requires access to the machine where the cluster node is running. In many cases, it creates too much burden because there are more people who have access to the database compared with the number of peo...