Ideas

Consider allowing read only replicas to connect to single node deployments. Currently, this is not possible because replication is disabled on single node databases.

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

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

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

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

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

test

test