#1 India's Top IT Training Institute

×

About Uncodemy

Know more about who we are and what we stand for.

About Us

About Us

Discover our mission to equip individuals with essential IT skills and industry expertise.

Read More →
UnCodeMy Gallery

UnCodeMy Gallery

Explore highlights from our IT training sessions and success stories.

Read More →
×

Free Resources

Learn, practice and plan your career — bilkul free.

Tutorials

Tutorials

Step-by-step written tutorials to learn any technology at your own pace.

Read More →
Free Counselling

Free Counselling

Book a free video counselling session and pick the right course for you.

Read More →
Online Compiler

Online Compiler

Write, run and test your code online — no setup required.

Read More →
Horizontal Scaling, Shard Keys, and Distributed Data Storage

MongoDB Sharding

As data grows beyond what a single server can handle, sharding distributes data horizontally across multiple machines — enabling MongoDB to scale to massive datasets and high throughput.

1. Sharded Cluster Architecture

ComponentRole
ShardStores a subset of the sharded data (often a replica set itself)
mongos (Router)Routes queries to the correct shard(s)
Config ServersStore cluster metadata and chunk mapping

2. Choosing a Shard Key

The shard key determines how documents are distributed across shards. A good shard key has high cardinality, even distribution, and matches common query patterns.

sh.shardCollection("ecommerceDB.orders", { customerId: "hashed" })
Shard Key StrategyProsCons
RangedEfficient range queriesRisk of "hot" shards for sequential keys
HashedEven data distributionRange queries scatter across all shards
Common Issue: Choosing a monotonically increasing shard key (like a timestamp) causes all new writes to land on the same shard, creating a "hot" shard bottleneck.

3. Enabling Sharding

// Enable sharding on a database
sh.enableSharding("ecommerceDB")

// Shard a collection with a chosen key
sh.shardCollection("ecommerceDB.products", { category: 1, _id: 1 })

// Check shard distribution
sh.status()

4. Chunks and Balancing

Data within a sharded collection is split into chunks based on shard key ranges. The balancer automatically migrates chunks between shards to keep data evenly distributed.

5. When to Shard

  • Your working data set exceeds available RAM on a single server
  • Write throughput exceeds what a single primary can handle
  • You need to distribute data geographically for lower latency
Pro Tip: Don't shard prematurely. Sharding adds operational complexity — first optimize indexes, query patterns, and consider vertical scaling or read replicas.

6. Sharding Checklist

  • ✅ Understand shards, mongos, and config servers
  • ✅ Choose a shard key with high cardinality and even distribution
  • ✅ Enable sharding on a database and collection
  • ✅ Understand chunks and the balancer
  • ✅ Know when sharding is (and isn't) the right solution
Key Takeaway: Sharding unlocks horizontal scalability, but the shard key decision is nearly permanent and hugely consequential — choose it based on real query and write patterns, not guesswork.

Ready to master MongoDB?

Build real-world MongoDB-powered applications with hands-on projects, mentor-led sessions, and placement support.

Explore Course