Change-Impact Analysis for a Cross-Service API Migration
Overview
What this challenge is about.
Pull API logs over 30 days from the API gateway to enumerate all consumers + per-endpoint call volume. Cross-reference with service-catalog ownership to map 23 consumers to teams. Run static analysis on consumer repos (where available) to identify which endpoints + fields they actually use. Predict failure surface per consumer (which fields they parse, which break under v3 schema). Design the migration: parallel-run v2/v3 for 8 weeks, dual-write for state-mutating endpoints, sunset cadence with 4 reminder waves. Author a 12-week coordination plan with per-team owner, weekly sync cadence, and a single dashboard showing migration progress per consumer. Deliver consumer map, impact analysis, migration design, and coordination plan.
The Brief
What you'll do, and what you'll demonstrate.
Run change-impact analysis on a v2→v3 API migration spanning 23 consumers and design a 12-week coordination plan with measurable safety nets.
Earning criteria — what you'll demonstrate
- Map cross-service API consumers from gateway logs + service catalog
- Predict failure surfaces from consumer-side static analysis
- Design a multi-mode migration path (parallel-run + dual-write + sunset)
- Coordinate a 12-week migration across 11 teams without it stalling
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.