Do they have only one huge table in the db that contains all of their entities? From the key structure that seems reasonable: shard id, type, object id.
If that is the case, is a relational db still the right place to keep such data? It seems that if the goal is to store this kind of data in one or a few huge sharded tables, a different tool could be optimizing to do the job better.
If that is the case, is a relational db still the right place to keep such data? It seems that if the goal is to store this kind of data in one or a few huge sharded tables, a different tool could be optimizing to do the job better.
It seems that I’m missing something…