Choosing a good shard key in MongoDB - Step-by-Step Execution

Concept Flow - Choosing a good shard key

Start: Need to shard collection

↓

Analyze data access patterns

↓

Identify candidate shard keys

↓

Evaluate shard key properties

↓

Shard collection using chosen key

↓

Monitor performance and rebalance if needed

This flow shows how to pick a shard key by analyzing data and queries, then choosing a key that balances data and query load well.

Execution Sample

MongoDB

db.orders.createIndex({ orderDate: 1 })
db.orders.createIndex({ customerId: 1 })
db.orders.createIndex({ region: 1 })

// Choose shard key based on query and data
sh.shardCollection("shop.orders", { customerId: 1 })

This example creates indexes and chooses customerId as the shard key for balanced distribution and query efficiency.

Execution Table

Step	Action	Evaluation	Result
1	Analyze query patterns	Queries mostly filter by customerId	customerId is a good candidate
2	Check cardinality	customerId has many unique values	High cardinality confirmed
3	Check data distribution	Orders spread evenly across customers	Even data distribution
4	Check write frequency	Writes are frequent per customer	Shard key supports write scaling
5	Choose shard key	customerId meets all criteria	Shard key set to customerId
6	Shard collection	Run sh.shardCollection command	Collection sharded on customerId
7	Monitor	Check chunk distribution and query performance	Balanced load observed
8	Exit	Shard key chosen and applied	Sharding setup complete

💡 Shard key chosen after confirming it supports balanced data and query load

Variable Tracker

Variable	Start	After Step 1	After Step 2	After Step 3	After Step 4	Final
candidateShardKey	none	customerId	customerId	customerId	customerId	customerId
cardinality	unknown	unknown	high	high	high	high
dataDistribution	unknown	unknown	unknown	even	even	even
writeFrequency	unknown	unknown	unknown	unknown	frequent	frequent

Key Moments - 3 Insights

Why is high cardinality important for a shard key?

High cardinality means many unique values, which helps distribute data evenly across shards, as shown in execution_table step 2.

Can a shard key with low query usage still be good?

No, a shard key should be used often in queries to route requests efficiently, as seen in step 1 where query patterns guide the choice.

What happens if data distribution is uneven?

Uneven distribution causes some shards to be overloaded, reducing performance. Step 3 checks for even distribution to avoid this.

Visual Quiz - 3 Questions

Look at the execution_table, what is the candidate shard key after Step 1?

A orderDate

B customerId

C region

D none

💡 Hint

Check the 'Evaluation' column in Step 1 of execution_table

At which step does the evaluation confirm high cardinality?

A Step 1

B Step 3

C Step 2

D Step 4

💡 Hint

Look at the 'Evaluation' column for the step mentioning cardinality

If queries mostly filtered by region instead of customerId, what would change in the variable_tracker?

A candidateShardKey would be 'region'

B cardinality would be 'low'

C dataDistribution would be 'uneven'

D writeFrequency would be 'infrequent'

💡 Hint

Refer to candidateShardKey values in variable_tracker and how query patterns affect it

Concept Snapshot

Choosing a good shard key:
- Analyze query patterns and data
- Pick a key with high cardinality
- Ensure even data distribution
- Use a key frequently in queries
- Shard collection with chosen key
- Monitor and rebalance if needed

Full Transcript

Choosing a good shard key in MongoDB involves analyzing how data is accessed and distributed. First, look at which fields queries use most often. Then check if those fields have many unique values (high cardinality) to spread data evenly. Also, ensure data is balanced across shards to avoid hotspots. Finally, pick a shard key that supports your write and read patterns well. This process helps keep your database fast and scalable.