Horizontal scaling made easy | Architectural simplification

Description

Manual database sharding is hard. But it doesn't have to be that way. In this series focused on how you can simplify your software stack, our Technical Evangelist Rob Reid walks through this painful process firsthand so you don't have to. Rob starts at one node before scaling to two, three, and eventually six. You'll get a full comparison of CockroachDB vs Postgres when it comes to scaling, see what manual sharding actually looks like, get an inside look at how manual database sharding impacts latency, and why CockroachDB can make horizontal sharding of data to achieve scale so much simpler. Horizontal scaling made easy | Architectural simplification 00:00 Introduction 00:42 What does horizontal scaling look like and why do you have to shard? 01:31 The Go application Rob is using for testing 01:41 Creating a Postgres node and customer table 02:16 What happens when you add 1 new node to the Postgres cluster? 05:26 What happens when you scale to 3 nodes? 08:10 What happens when you scale to 6 nodes from 3 nodes?? 09:33 The hierarchy of sharding explained via diagram 10:28 (Continued) Scaling from 3 nodes to 6 nodes 12:43 Why manual database sharding is never the answer 15:30 How does CockroachDB handle sharding? Additional resources: ✔️ What is CockroachDB? https://cockroa.ch/42uaZ9G ✔️ REGIONAL BY ROW in CockroachDB: https://www.cockroachlabs.com/blog/data-homing-in-cockroachdb/ ✔️ CockroachDB architecture overview: https://cockroa.ch/3RzIvrh ******************************** Follow Cockroach Labs ✔️ Website: https://cockroachlabs.com/ ✔️ Twitter (X): https://twitter.com/cockroachdb ✔️ Linkedin: https://www.linkedin.com/company/cockroach-labs/ ✔️ Facebook: https://www.facebook.com/cockroachlabs ✔️ Instagram: https://www.instagram.com/cockroachdb ✔️ Threads: https://www.threads.net/@cockroachdb