Ideas

Have a component that would allow developers to register their events schema in the registry. When appending new events, when the schema id is provided, the event is checked for compatibility with the schema, and it it's not compatible, the append...

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.

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

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