Greetings,
I will look into it deeper (as its an interesting view).
but for my understanding:
- partition can be 10 GB in size and the database can be N partitions.
so if we got 20 GB's of financial records we need to shard it over 2 partitions.
and the 2 partitions will go on different instances, depending on their activity they will be moved to appropriate server.
now we also got 2 GB of users, 5gb of costumer records.
these will be 2 partitions, however they will be hosted on the same PC.
So while 10gb is a "hard" limited for a single instance, its only for 1 partition. as SDS will spread its data over multiple instances with 1 entry point to keep track of the partitions and instances.
This Entry point has now 4 partition registered, with 3 seperated endpoints linked to the partition.
This is, to my knowledge, how the speed and replication is keep in tracks with even the largest database.
Kind Regards,
Sebastian