Overview
What this challenge is about.
Analyze schema (32 tables) + query workload (anonymized 7-day pg_stat_statements export) to identify the right shard key per table. Most tables shard on user_id; identify the 4-6 tables that cannot (likely candidates: catalog, feature flags, audit log) and propose either a global table strategy or a separate unsharded service. Prototype the routing layer in Go (or use Vitess vtgate as a reference implementation). Design a dual-write migration with read-shadowing validation. Deliver a 15-page design doc, routing prototype, and a 6-month migration runbook with rollback gates per phase.
The Brief
What you'll do, and what you'll demonstrate.
Design and prototype a 16-shard PostgreSQL topology with a routing layer plus a 6-month dual-write migration path that does not require maintenance windows.
Earning criteria — what you'll demonstrate
- Choose shard keys based on query patterns, not assumed access patterns
- Reason about cross-shard transactions and avoid them by design
- Design a zero-downtime dual-write migration with verification at every phase
- Document a multi-quarter migration in a form the on-call team will trust
Program Fit
Where this fits in your program.
Sharpens the same skills your degree expects you to demonstrate.
Skills
Skills you'll demonstrate.
Each one shows up on your verified credential.
Careers
Roles this prepares you for.
Real titles. Real skill bridges. Pick the one closest to your trajectory.
Career mappings coming soon.