Migrate a RabbitMQ Topology to Kafka for a Healthcare SaaS
Overview
What this challenge is about.
Analyze the current RabbitMQ topology + 30 days of message volume data. Map each queue to a Kafka topic with the right partition key (likely patient_id, encounter_id, or clinic_id depending on stream). Build a dual-publish bridge in Go: publisher writes to both, consumers can be flipped one at a time. Build replay tooling for backfilling Kafka with the last 30 days of RabbitMQ messages. Prototype against the patient-encounter stream end-to-end. Deliver 10-page writeup, prototype source, and a 60-day phased cutover plan with rollback gates.
The Brief
What you'll do, and what you'll demonstrate.
Migrate a 24-queue RabbitMQ topology to Kafka with dual-publish + dual-consume bridge and a 60-day phased cutover that guarantees zero event loss.
Earning criteria — what you'll demonstrate
- Map a RabbitMQ topology to Kafka topics + partitions correctly
- Build a dual-publish bridge that survives both broker failures
- Design replay tooling that respects ordering and idempotency
- Sequence a multi-service broker migration without dropping events
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.