Discovering Sharding
When a successful product is online for some years, the amount of data stored in the relational database will get very big. In a company I worked for, a single table occupied a grand total of 600 TB. Yes, TB as in terabytes, like 1000 GB. Good luck trying to do anything with that!
While that scale is not that common, having issues with tables that have grown too big is certainly not infrequent. Whenever you find yourself in a situation like that, you will probably feel the temptation to modify the tables—and with them, the data model—not for syntactical reasons, but just to make the data “fit.” For example, some information that is embedded in the model table is sent to a different table, becoming an associated object instead. ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access