the vast, vast majority of use cases do not require that level of sharding, so we simply did not do it. if/when it becomes necessary, we'll likely evaluate that as a possible optimization around data storage and retrieval, although it makes certain kinds of operations much, much harder to do efficiently (mostly reverse walks)