Hi Andy,
Kudos for your support and enthusiasm.
In the pipeline:
-
dynamic store support: currently there is a one-store-per-cluster (1SPC) limitation, steered by config. In the philosophy of ExESDB a store supports one business process/behavior (one aggregate type). If you are familiar with EventStoreDB, a ‘store’ in ExESDB corresponds to a ‘category’ in EventStoreDB. Though there is much to say for 1SPC, N-stores-per-cluster (NSPC) offers more options towards scenarios with budget constraints (less nodes), resource constraints (smaller hardware) and simplified inter-business process/behavior communication (less complexity)
-
An ExESDB Admin API (REST+gRPC) in order to support:
-
an ExESDB Administration tool: not sure yet in what format…probably a CLI for scripting (must have!), a TUI (I am a terminal jockey) and/or an Admin Web UI/Dashboard with fancy metrics and such
Later:
A REST/gRPC API that is 100% compatible with EventStoreDB, so it could form a ‘drop-in’ replacement. Since ExESDB supports dynamic clustering and is resilient against node shutdowns, I figure it has the advantage over EventStoreDB for Orchestrated scenarios (Kubernetes for instance)
All this is of course just a wishlist and it is a labor of love, so I won’t put planning on it 
