Kafka & Event-Driven Systems
Design and build an order-event pipeline while learning topics, partitions, consumer groups, retries, and idempotent processing.
Production project
Order Processing Event Pipeline
An order platform must notify payment, inventory, and notification workflows without coupling every service through blocking HTTP calls.
Who this is for
- •Backend engineers moving beyond synchronous REST calls
- •Developers preparing for distributed-system design discussions
How this helps
- •You can design event-driven flows with fewer hand-wavy boxes
- •You can reason about reliability beyond the happy path
What you will learn
The capabilities, not just the keywords.
- •Explain when asynchronous events are better than synchronous calls
- •Model Kafka topics and event payloads
- •Understand partitions and consumer groups
- •Design retry and duplicate-handling strategies
- •Trace an event across a multi-service workflow
Real production project
Order Processing Event Pipeline
An order platform must notify payment, inventory, and notification workflows without coupling every service through blocking HTTP calls.
What we build
- •Order-created producer
- •inventory consumer
- •notification consumer
- •event schema
- •retry/idempotency discussion
Stack
- •Kafka
- •Docker
- •Java or Python sample services
Production concerns
- •Duplicate events
- •ordering
- •consumer failure
- •schema evolution
- •observability
- •dead-letter handling
Finished deliverables
- •Runnable event flow
- •event contract
- •architecture diagram
- •failure-mode checklist
Prerequisites
Required
- •Comfort building or reading backend APIs
Helpful, but optional
- •Docker familiarity
- •Java or Python backend experience
Before the session
Come ready to build.
- •Docker Desktop
- •Java 17+ or Python 3.11+
- •Git
What to expect
What you get
Something useful after the call ends.
- •Source code
- •event contract template
- •architecture diagram
- •production trade-off notes
Where to go next
Backend → Event-Driven Architecture → Distributed Systems
Every session can be booked independently. If you already know the prerequisite material, skip ahead.
Useful before this
No earlier session is mandatory.
Good next steps
Teaching proof
Review the evidence first.
See workshop delivery, technical projects, and teaching proof before booking.
Ready?
Request BE06: Kafka & Event-Driven Systems
Share your current level and what you want to build. The session can be adapted without changing its core outcome.
Request this sessionFAQ
Can I book only this session?
Yes. Every session is designed to work independently.
Can I bring my own project?
Yes, when it fits the session outcome. We can map the concepts onto your project instead of the default example.
What if I already know part of the topic?
We can move faster through familiar material and spend more time on implementation, failure modes, and production trade-offs.
Is the session recorded?
Recording is not promised by default. Confirm this before the session if you need it.
What should I install?
The preparation section above lists the default setup. You will receive any session-specific setup notes before the call.
Are API or cloud charges included?
No. Any third-party API or cloud usage is paid directly through your own account unless explicitly agreed otherwise.