Sharding splits a single database into multiple smaller databases, each holding a subset of the data. Instead of one PostgreSQL instance handling 500 million rows, you spread them across five instances of 100 million rows each.

The idea is simple. The execution is not.

This guide covers how sharding works, the common strategies, when it makes sense, and the operational cost most articles skip over.

What is database sharding?

Database sharding is a horizontal scaling technique that splits a s

Last9 is a  blog focusing on DevOps practices, cloud architecture, and software engineering methodologies. Through insightful articles, tutorials, and case studies, Last9 addresses various aspects of modern software development, including continuous integration and continuous delivery (CI/CD), infrastructure as code (IaC), containerization, and microservices architecture. By sharing best practices, real-world experiences, and expert insights, Last9 equips developers, DevOps engineers, and IT professionals with the knowledge and tools needed to build, deploy, and manage resilient and scalable cloud-native applications.

Last9

Database sharding is a horizontal scaling technique that distributes data across multiple database instances using a shard key. The guide covers the four main sharding strategies—hash-based, range-based, directory-based, and geographic—along with how to pick an effective shard key based on cardinality, distribution, and query alignment. It emphasizes that sharding should be a last resort after exhausting vertical scaling, read replicas, indexing, query optimization, and partitioning. The real cost of sharding lies in operations: cross-shard scatter-gather queries, live rebalancing, coordinated schema migrations across all shards, and per-shard monitoring that multiplies metric cardinality. Database-specific options like Citus for PostgreSQL, Vitess for MySQL, and built-in sharding in MongoDB and distributed SQL databases (CockroachDB, TiDB, YugabyteDB) are also compared.

Database Sharding: How It Works and When You Actually Need It

See Every Database in Your Cloud from One Place