Archiving / Sharding ideas?

EventStoreDB
1

I’m wondering what strategy people use to shard their event store(s)? Could be for archiving, or geo location, or customers, or … Any other reason.

Maybe there is thought about partitioning multiple stores? Each store having it’s own stream, with a master head that knows the routing, and the ability to MoveStream(sourceStore, destinationStore) ???

I don’t have an immediate need, I’m just brainstorming futures.

@ScottCate
+1-602-418-0770

2

This has been part of the intended design from the start, the partition point would be the stream. We’re unlikely to actually build it until we have a customer who has committed to paying for it though as it’s a reasonable amount of work to do properly!

3

This would also include support for projections on many nodes btw.