Guided Lab Brief

Partitioning & Sharding

Route traffic across shard domains while keeping lookup and rebalance metadata explicit.

Start LabReview ChapterBrowse Guided Labs

Overview

Route traffic across shard domains while keeping lookup and rebalance metadata explicit.

Partitioning fails when routing is implicit.

You will build 7 architecture steps that model production dependencies.

You will run 1 failure experiment to observe bottlenecks and recovery behavior.

Success target: Router routes deterministically under skew while rebalance remains controlled and observable.

Learning Objectives

  • Can defend partition routing design under growth
  • Can explain shard-map consistency tradeoffs
  • Can discuss rebalance safety controls in interviews

Experiments

  1. Make shard map TTL too long and observe stale routing after rebalance

Failure Modes to Trigger

  • Trigger: Make shard map TTL too long and observe stale routing after rebalance

    Observe: Router keeps stale ownership and writes to old shard targets after movement.

Next Guided LabReinforce with Quizzes