Tune Consistency Levels for a Global Ride-Hailing Platform
Overview
What this challenge is about.
Receive an anonymized topology export (3 regions, RF=3 per region) plus 7 days of query traces tagged by class. Reproduce the matching anomaly in a Kubernetes-based test cluster, varying read/write consistency from ONE through QUORUM and LOCAL_QUORUM. Measure p50/p99 latency, staleness windows, and behavior during a simulated single-AZ outage. Recommend a per-query-class consistency policy with explicit rationale tied to CAP (Consistency, Availability, Partition tolerance) tradeoffs. Deliver a 10-page analysis, a tunable parameters table, and a 4-week phased rollout plan.
The Brief
What you'll do, and what you'll demonstrate.
Tune Cassandra consistency per query class to cut p99 matching latency by 20 percent while keeping payments strictly correct under regional partitions.
Earning criteria — what you'll demonstrate
- Apply CAP and PACELC reasoning to a real multi-region datastore
- Measure the latency-vs-staleness curve under realistic load mixes
- Distinguish per-query consistency needs from system-wide defaults
- Design a safe rollout when correctness regressions are visible to end users
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.