100% Free Forever
AI-Powered Learning
Industry Expert Content
Certificates & Badges
Learn At Your Own Pace

Database Sharding Cheat Sheet

Database Sharding Cheat Sheet

Covers horizontal partitioning strategies, shard key selection, routing, and rebalancing for scaling databases across multiple nodes.

2 PagesAdvancedMar 12, 2026

Sharding Strategies

Common approaches to splitting data across shards.

  • Range-based sharding- Partitions data by key ranges (e.g., user_id 1-1M on shard A); simple but prone to hotspots on sequential keys
  • Hash-based sharding- Applies a hash function to the shard key to evenly distribute rows; loses range-query locality
  • Directory-based sharding- A lookup service maps each key to its shard, allowing flexible rebalancing at the cost of an extra hop
  • Geo-sharding- Partitions by region/location to reduce latency and satisfy data-residency requirements
  • Consistent hashing- Maps shards and keys onto a hash ring so adding/removing a shard only remaps a fraction of keys
  • Shard key- The column(s) used to determine which shard a row lives on; picking it wrong causes hotspots or cross-shard joins

Hash-Based Shard Routing

Route a request to its shard using a hash of the key.

python
import hashlibdef get_shard(user_id: str, num_shards: int) -> int:    # Consistent hash of the key mod number of shards    digest = hashlib.md5(user_id.encode()).hexdigest()    return int(digest, 16) % num_shards# Route a query to the correct shard connectionshard_id = get_shard("user_42", num_shards=8)conn = shard_connections[shard_id]conn.execute("SELECT * FROM orders WHERE user_id = %s", ("user_42",))

Consistent Hashing Ring

Minimize key remapping when shards are added or removed.

python
import bisectimport hashlibclass HashRing:    def __init__(self, nodes, vnodes=100):        self.ring = {}        self.sorted_keys = []        for node in nodes:            for i in range(vnodes):                key = self._hash(f"{node}:{i}")                self.ring[key] = node                bisect.insort(self.sorted_keys, key)    def _hash(self, key):        return int(hashlib.md5(key.encode()).hexdigest(), 16)    def get_node(self, key):        h = self._hash(key)        idx = bisect.bisect(self.sorted_keys, h) % len(self.sorted_keys)        return self.ring[self.sorted_keys[idx]]

Common Pitfalls

Issues that surface once a sharded system is in production.

  • Cross-shard joins- Joining rows that live on different shards requires app-level fan-out or a scatter-gather query; avoid by denormalizing
  • Hotspotting- A poorly chosen key (e.g., monotonically increasing IDs) concentrates writes on one shard
  • Rebalancing cost- Adding shards without consistent hashing forces a full data reshuffle; plan capacity ahead of time
  • Distributed transactions- Multi-shard writes need two-phase commit or sagas since native ACID transactions don't span shards
  • Global secondary indexes- Queries on non-shard-key columns require a separate index service or scatter-gather across all shards

Zero-Downtime Resharding: Dual-Write + Backfill

The standard playbook for moving from N to M shards without an outage.

python
def write_during_migration(key, value):    old_shard = get_shard(key, num_shards=OLD_N)    new_shard = get_shard(key, num_shards=NEW_N)    write(old_shard, key, value)    write(new_shard, key, value)  # dual-write so both topologies stay currentdef backfill(old_shards, new_shards):    # Copy historical rows written before dual-write was enabled    for row in scan_all(old_shards):        target = get_shard(row.key, num_shards=NEW_N)        upsert(target, row)  # idempotent write, safe to re-run# Cutover sequence:# 1. Enable dual-write.# 2. Backfill historical data into new shards.# 3. Verify row counts / checksums match between old and new.# 4. Flip reads to the new shard map.# 5. Stop writing to old shards, decommission.

Scatter-Gather for Cross-Shard Queries

Fan out a query to every shard and merge results in the application layer.

python
from concurrent.futures import ThreadPoolExecutordef scatter_gather_query(sql, params, shard_connections):    def query_one(conn):        with conn.cursor() as cur:            cur.execute(sql, params)            return cur.fetchall()    with ThreadPoolExecutor(max_workers=len(shard_connections)) as pool:        results = pool.map(query_one, shard_connections.values())    merged = [row for shard_rows in results for row in shard_rows]    # Sorting/aggregation (ORDER BY, LIMIT, GROUP BY) must be redone here    # since each shard only sorted/limited its own local rows.    return sorted(merged, key=lambda r: r["created_at"], reverse=True)

Choosing a Shard Key: Trade-offs

There is no perfect shard key — every choice sacrifices something.

  • tenant_id / customer_id- ideal for B2B SaaS: keeps all of a customer's data co-located for fast queries and simple compliance/data-residency boundaries, but risks large-tenant hotspots
  • Composite key (tenant_id + entity_id)- combines a low-cardinality routing prefix with a high-cardinality suffix to spread writes within a large tenant across sub-shards
  • Reverse-order / salted keys- prefixing a hash or random salt onto a monotonic ID (common in Bigtable/HBase schemas) prevents a single 'hot' region from absorbing all recent writes
  • Derived vs. natural keys- deriving the shard key from a hash of a natural key avoids exposing internal routing, but makes manual shard lookup/debugging harder
  • Re-shardability- a key chosen without consistent hashing or virtual nodes locks you into painful full-cluster reshuffles when capacity needs to change

Virtual Shards for Cheap Rebalancing

Decouple logical partitions from physical nodes so rebalancing is just moving assignments.

python
NUM_VIRTUAL_SHARDS = 4096  # fixed forever, far more than any physical node countdef virtual_shard(key: str) -> int:    return hash(key) % NUM_VIRTUAL_SHARDS# Small, static mapping updated as physical capacity changesvshard_to_node = {    0: "node-a", 1: "node-a", 2: "node-b", 3: "node-b",  # ... 4096 entries}def get_node(key: str) -> str:    return vshard_to_node[virtual_shard(key)]# Adding node-c: only reassign a subset of virtual shard entries (e.g.# 0..1365 -> node-c) instead of rehashing every key in the cluster.

Sharding vs. Related Techniques

Terms that get conflated but solve different problems.

  • Sharding (horizontal partitioning)- splits rows across independent database instances/nodes to scale writes and total data volume
  • Table partitioning- splits rows across sub-tables within a single database instance (e.g. Postgres declarative partitioning); improves query pruning and maintenance, doesn't add write capacity
  • Replication- copies the same full dataset to multiple nodes for availability/read scaling; every replica holds all the data, unlike a shard
  • Federation / functional partitioning- splits by feature/domain (e.g. users DB, orders DB) rather than by key range or hash
  • Sharded + replicated (typical production setup)- each shard is itself a replica set, so you get both horizontal write scaling and per-shard high availability
Pro Tip

Pick a shard key with high cardinality and even access patterns (e.g., a hashed user_id), not a monotonically increasing timestamp or auto-increment ID — those funnel all new writes onto the last shard.

Was this cheat sheet helpful?

Explore Topics

#DatabaseSharding#DatabaseShardingCheatSheet#Database#Advanced#ShardingStrategies#Hash#Based#Shard#Databases#CheatSheet#SkillVeris

Frequently Asked Questions

21 categories · pick one to explore

Does SkillVeris have a tech blog, and what does it cover?
Yes, the SkillVeris blog has over 500 articles covering AI and machine learning, programming, web development, DevOps, cloud, security, databases and career guidance. Articles are practical and answer-first, and many use the Learn Through Hobbies approach, teaching technical concepts through cricket, music, gaming or cooking analogies. Everything is free to read.
What is the SkillVeris tech glossary and how big is it?
The SkillVeris glossary is a free reference of roughly 2,000-plus technology terms, each with a clear plain-language definition. It spans AI, programming, web, DevOps, cloud, security and database vocabulary, so whenever a lesson, article or job description uses jargon you do not recognise, the glossary gives you a fast, reliable answer.
Are the developer cheat sheets on SkillVeris free to download?
The cheat sheets are completely free to use, like everything else on SkillVeris. Each sheet condenses a language or tool into its essential syntax, commands and patterns for quick reference while coding. They are designed for rapid lookup during real work, complementing the deeper explanations found in study notes and courses.
Which programming references and cheat sheets are available?
Cheat sheets cover the platform's main domains, including programming languages, AI and ML tooling, web development, DevOps, cloud, security and databases, matching the topics of the 37 live courses. Each sheet lists related reading links and hashtags, so you can jump from a quick reference into fuller study notes or blog articles.
How do I find the meaning of a technical term quickly?
Search the SkillVeris glossary, which holds around 2,000-plus terms with concise, plain-language definitions. Each entry gets to the point in its first sentence, then links to related reading like blog posts or study notes for deeper context. It is faster and more consistent than sifting through scattered search results.
Is the SkillVeris blog good for beginners learning to code?
Yes, many blog articles are written specifically for beginners, and the Learn Through Hobbies style makes them unusually approachable: you might learn Python concepts through cricket or understand APIs through cooking. With 500-plus articles across skill levels, beginners can start with fundamentals and keep reading as they advance, entirely free.
Can cheat sheets replace full courses for learning a language?
No, cheat sheets are references, not teaching tools; they assume you already understand the concepts and just need syntax or commands fast. To actually learn a language, take a structured SkillVeris course with its 24–40 lessons and assessments, then keep the cheat sheet beside you while practising in Code Lab.
How often are new blog articles published on SkillVeris?
The blog grows regularly and already exceeds 500 articles, with new posts added as courses launch and technologies evolve. Topics track the platform's catalogue across AI, programming, web development, DevOps, cloud and security, so checking the Blog section periodically surfaces fresh tutorials, explainers and career-focused pieces, all free to read.
Does the glossary cover AI and machine learning terms?
Yes, AI and machine learning vocabulary is a major part of the roughly 2,000-plus term glossary, covering everything from foundational terms to modern concepts around LLMs, RAG and MLOps. Definitions are plain-language and answer-first, which helps when dense AI papers or course lessons throw unfamiliar jargon at you.
Are there cheat sheets for interview preparation?
Cheat sheets work well as interview-day refreshers because they compress syntax, commands and key concepts into scannable references. For dedicated preparation, combine them with the SkillVeris interview questions feature, which includes readiness scoring, plus study notes for depth. Reviewing a relevant cheat sheet just before an interview steadies recall under pressure.
Can I read the tech blog without signing up?
Yes, the blog is freely readable, and SkillVeris never charges for content. All 500-plus articles are open, covering tutorials, concept explainers and career advice. Creating a free account adds value elsewhere on the platform, like course progress tracking and certificates, but reading the blog requires no commitment at all.
How is the SkillVeris glossary different from Wikipedia?
The glossary is purpose-built for learners: definitions are short, plain-language and answer-first, sized for a quick lookup mid-lesson rather than a deep encyclopedic read. Entries also cross-link to related SkillVeris study notes, blog posts and courses, so a definition becomes a doorway into structured learning instead of a dead end.
Do blog articles use the Learn Through Hobbies method?
Many blog articles teach technical topics through hobby analogies, a hallmark of the SkillVeris blog, so you will find articles explaining programming through cricket, machine learning through music, or system design through cooking. The analogy is the teaching device; the article still delivers the real technical concept underneath.
Where can I find quick programming references while coding?
Open the SkillVeris cheat sheets, which are built exactly for that moment: compact, scannable references for syntax, commands and common patterns across languages and tools. Keep the relevant sheet in a browser tab while you work in Code Lab or your own editor, and dip into the glossary for terminology.
Is there a glossary entry for terms I meet in job descriptions?
Very likely yes, with roughly 2,000-plus terms across AI, programming, web, DevOps, cloud, security and databases, the glossary covers most jargon that appears in tech job descriptions. Decoding a listing this way helps you judge role fit honestly and prepares you to discuss those terms in interviews.
Are the blog articles written for the Indian tech audience?
The blog serves Indian learners plus a worldwide audience. Content stays globally relevant while acknowledging realities that matter in India, such as free access being essential for students and freshers, and career guidance that connects naturally to the SkillVeris jobs portal, which aggregates roles across India, UK, USA, Germany and Remote.
Can I suggest a topic for the blog or glossary?
SkillVeris content grows in response to what learners need, so feedback is welcome through the platform's support channels. If a term is missing from the glossary or a topic deserves an article, telling the team helps prioritise it. Meanwhile, the AI Mentor can answer the question immediately, 24/7, at any depth.
Do cheat sheets and glossary entries link to deeper learning?
Yes, every cheat sheet and glossary entry carries related reading links into study notes, blog articles and courses, plus concept hashtags for discovering similar content. This cross-linking means a thirty-second lookup can smoothly become a structured learning session whenever you decide you want more than a quick answer.
What makes SkillVeris programming references trustworthy?
The references are written to strict internal quality standards, kept consistent with the platform's 37 live courses, and never padded with invented statistics or hype. Definitions and cheat sheets are reviewed against the same content contracts that govern courses, and the answer-first style makes any inaccuracy easy to spot and correct.
How do the blog, glossary and cheat sheets fit into my learning routine?
Use them as satellites around your main course: read blog articles for context and motivation, hit the glossary the instant jargon appears, and keep cheat sheets open while coding. Together with study notes, Code Lab and the 24/7 AI Mentor, they turn passive reading into a complete, free learning system.

What Learners Say

Real journeys from the SkillVeris community — swipe for more.

SkillVeris taught me Python through Cricket. Now I’m building real projects and feeling confident!
Arjun S. · B.Tech Student
The best platform for hobby-based learning. Concepts finally stick.
Priya R. · Data Analyst
I went from zero coding to a portfolio of projects — all by learning through my love for gaming. Landed my first internship!
Kabir M. · CS Undergraduate
Trending Topics50 popular tags — tap to explore
Trending CoursesAll 37 free courses — tap to browse