Overview
What this challenge is about.
Design an event-driven architecture using a Kafka-like message bus (anonymized: assume a Kafka-compatible event log). Define: 9 event types with Avro schemas, partition strategy, ordering guarantees per partition, idempotent consumer patterns, dead-letter handling, and saga choreography for compensating actions. Walk through 5 failure modes (consumer down, message poison, schema evolution, slow consumer, duplicate). Deliver: target architecture diagram (C4 model), 9 Avro schemas, 6 ADRs (one per significant decision), failure-mode walkthroughs, and a phased migration plan from the current synchronous pipeline.
The Brief
What you'll do, and what you'll demonstrate.
Design an event-driven order-to-cash architecture with explicit choreography, schema evolution, and 5 named failure-mode mitigations.
Earning criteria — what you'll demonstrate
- Design event-driven architectures with choreography vs orchestration trade-offs
- Specify Avro schemas with forward/backward-compatible evolution rules
- Apply saga patterns for distributed transactions with compensating actions
- Document architecture decisions with ADRs that survive team turnover
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.