Event-Driven Order Processing System
Build a Kafka-based event-driven order processor with sagas, idempotency, and exactly-once semantics.
About this project
Event-driven architecture is the senior-backend interview pattern. This project builds a small but real implementation: an order-processing system with separate services for orders, payments, inventory, and notifications, communicating via Kafka. You will implement the saga pattern for distributed transactions, idempotency keys, dead-letter queues, and the operational tail (consumer-lag monitoring, replay on failure).
Why build this in 2026?
Event-driven systems are how AI-heavy backends are now structured (the LLM call is async, the agent might run for 30s). Strong differentiator.
What you'll ship
- Multi-service GitHub repo
Sign up to see the full project brief
Full deliverables, success criteria, and AI Career Tutor support — free.
You'll unlock:Complete project brief, AI tutor that knows this project, and progress tracking when you start.