Architecture in practice
Explain where an order goes
Show the producer, topic and consumer in one runnable order-processing example.
For Kafka and event-driven platform teams
Work through a real model.
Open the example, follow its connections and make a change. Edits save in a separate browser draft. Your main draft remains unchanged.
Start from this example
Follow an accepted order
The API publishes an order event to orders.v1. A fulfilment worker consumes it later. Showing the topic as a separate component makes the asynchronous boundary explicit and gives the team a place to discuss what happens after the API responds.
Add the operational questions
What if the worker is unavailable? Can an event be delivered twice? Where does an invalid order go? Add the retry path, dead-letter destination and ownership notes that reflect your actual system. The starter intentionally leaves those decisions to you.
Check the story against the implementation
Ask an engineer to compare the labels and endpoints with the producer and consumer configuration. The animated path explains your chosen design; it does not verify runtime behaviour. Keep the source with the review notes for the next change.
Take the next step.
Use the task guide for the exact controls and permissions. Keep a portable export when you have made a change you want to preserve.
Read the task guideExplore another model