System design
Database sharding vs partitioning: scaling past one server
When a table grows past 500 million rows, partitioning keeps query plans fast on one server while sharding scales writes across a cluster at the cost of ACID.
The engineering questions you get asked, and the bugs you actually hit. Drawn, one mechanism at a time, in the order the videos ship.
When a table grows past 500 million rows, partitioning keeps query plans fast on one server while sharding scales writes across a cluster at the cost of ACID.