Ideas

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.

Current implementation of read-only replicas require them to be connected to the cluster. It means that every new replica adds some overhead to the operational cluster nodes, particularly its leader. It creates limitation of the feature as one mig...

Move custom and standard projections to Connectors.

Focus on removing linkto eventsIncludes sequence numbers$allcategoryguarantees on write (optional consistency) from a client perspective also defined by user?

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

ESDB currently supports only RSA keys in certificates when specifying --certificate-private-key-file. The advantage of using EC keys would be that the key is much smaller for the same security level (EC takes 256 bit vs RSA 2048 bit for same secur...

Implement backup and restore as database functions.

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