> The size of the shards depends on the data. You're right. What I meant was that a 'shard' in actordb isn't meant to be 'all data on one machine/node' - which

> The size of the shards depends on the data. You're right. What I meant was that a 'shard' in actordb isn't meant to be 'all data on one machine/node' - which is how many other databases view sharding, but is expected to be much more fine-grained. Thanks for the other explanations. Another interesting implementation aspect is its use of LMDB for storing the SQLite pages.