Design Schema Evolution for a Multi-Tenant Event Platform
Overview
What this challenge is about.
Design a schema-evolution model covering: schema-registry topology (per-tenant subjects vs shared), compatibility modes per topic class (strict vs forward-only vs none), tenant-onboarding policy, deprecation timeline. Implement a CI-time compatibility checker that runs against every PR touching event schemas (use Buf for Protobuf or the Confluent schema-registry CLI for Avro). Build a runtime schema-violation alerter. Deliver 12-page writeup, working CI checker, and tenant-onboarding policy doc.
The Brief
What you'll do, and what you'll demonstrate.
Design and ship a schema-evolution governance model + CI-time compatibility checker for a multi-tenant Kafka platform processing ~2B events/month.
Earning criteria — what you'll demonstrate
- Design schema-registry topology for multi-tenant event platforms
- Choose per-topic compatibility modes based on consumer assumptions
- Build CI-time enforcement that prevents breakage before merge
- Communicate schema policy to non-technical customer-facing teams
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.