Bridge a Healthcare Messaging System from RabbitMQ to Kafka
Overview
What this challenge is about.
Bridge a Healthcare Messaging System from RabbitMQ to Kafka. Advanced challenge in code. Writing production code that solves real engineering problems, earn ...
The Brief
What you'll do, and what you'll demonstrate.
Move a 24-queue RabbitMQ messaging system to Kafka using a dual-publish and dual-consume bridge and a phased 60-day cutover that guarantees zero downtime and zero lost events.
This is not a coding exercise. It is the work a software engineer does between a Jira ticket and a merged PR. That distinction matters to every hiring manager who has seen candidates solve LeetCode problems and none who have shipped production code under real constraints.
When you finish, you will have something most graduates do not: a real-world deliverable, verified by Ewance, that you can show to a hiring manager and say "I did this. Here is the proof."
Earning criteria — what you'll demonstrate
- Translate an existing queue topology into a Kafka topic and partition design that preserves required ordering
- Implement a dual-write bridge that keeps two messaging systems consistent during migration
- Build event-replay and reconciliation tooling that proves zero event loss against a source of truth
- Design a reversible, phased cutover with concrete rollback gates under a zero-downtime constraint
- Communicate a high-risk infrastructure migration clearly to both engineers and stakeholders
Program Fit
Where this fits in your program.
Sharpens the same skills your degree expects you to demonstrate.
Aligned coursework coming soon.
Skills
Skills you'll demonstrate.
Each one shows up on your verified credential.
- Kafka
Apply kafka to solve real industry problems and demonstrate production-level capability.
- Rabbitmq
Apply rabbitmq to solve real industry problems and demonstrate production-level capability.
- Message Broker Migration
Apply message broker migration to solve real industry problems and demonstrate production-level capability.
- Partition Design
Apply partition design to solve real industry problems and demonstrate production-level capability.
- Dual Write Migration
Apply dual write migration to solve real industry problems and demonstrate production-level capability.
- Event Replay
Apply event replay to solve real industry problems and demonstrate production-level capability.
Careers
Career paths this challenge builds toward
Completing this challenge demonstrates skills that transfer directly to these roles:
Backend Engineer (Distributed Systems)
You practice the exact work of evolving a production messaging backbone without downtime: mapping topologies, designing partitions, and writing bridge code that keeps two systems consistent. This mirrors the reliability-critical backend work expected of senior distributed-systems engineers.
This challenge sharpens
- kafka
- partition-design
- dual-write-migration
Platform / Infrastructure Engineer
Migrating brokers under a zero-loss constraint with phased rollback gates is core platform work. You build the muscle for planning reversible infrastructure changes and proving safety with tooling, which is what platform teams hire for.
This challenge sharpens
- message-broker-migration
- rabbitmq
- kafka
Data Engineer (Streaming)
Replay, reconciliation, and partition design are everyday concerns in streaming data pipelines. This challenge builds direct experience backfilling and validating event streams against a source of truth, a key competency for streaming-focused data engineers.
This challenge sharpens
- event-replay
- kafka
- partition-design