Event-driven architecture template

Producers publish facts to a broker; independent consumers react — with the design rules that keep it reliable.

Use this templateFree, opens in your browser. No sign-up.

Event-driven architecture template
Design rules
Order service
Payment service
User service
Event broker (Kafka) topics: orders, payments, users
Email notifications
Analytics → data warehouse
Inventory service
Fraud detection
Producers
Consumers
Events are past-tense facts: OrderPlaced
Schema registry + versioned schemas
Consumers are idempotent (at-least-once delivery)
Dead-letter topic + replay for failures
Outbox pattern: save + publish atomically
Event-driven architecture
OrderPlaced
PaymentCaptured
UserSignedUp
orders, users
all topics
orders
payments
The event-driven architecture template as it opens in Kelvo: 8 boxes, 5 sticky notes and 7 links.

What's on the board

Design rules
Events are past-tense facts: OrderPlaced · Schema registry + versioned schemas · Consumers are idempotent (at-least-once delivery) · Dead-letter topic + replay for failures · Outbox pattern: save + publish atomically

Also on the board

  • Producers
  • Consumers
  • Email notifications
  • Order service
  • Analytics → data warehouse
  • Event broker (Kafka) topics: orders, payments, users
  • Payment service
  • Inventory service
  • User service
  • Fraud detection

How to use this template

  1. Click Use this template. It opens in the Kelvo app as a new board, saved in your browser.
  2. Double-click any box to change its text. Replace the examples with your own content.
  3. Sketch, then convert. Draw boxes and arrows with the pen, select the strokes and click Convert sketch: they become real boxes and links.
  4. Ask Kelvo right on the board (Pro). With Pro, type @kelvo and what you want in any box or text, for example “@kelvo add error handling”, and press Enter. The change is made there and the request disappears; ⌘Z undoes it.
  5. One page per level. Put the C4 context view on one page and the container view on the next, so each diagram stays readable.

Good for

  • architect
  • event-driven
  • kafka
  • messaging
  • architecture
  • Agreeing on boundaries and responsibilities between services
  • Recording why a design was chosen (and what was rejected)
  • Comparing integration options side by side

Related templates

  • C4 system context diagram template previewC4 system context diagram

    C4 level 1: the system in scope, the people who use it and the external systems it depends on, with a legend.

  • C4 container diagram template previewC4 container diagram

    C4 level 2: the apps, APIs, databases and queues inside the system boundary, with the technology on each link.

  • Microservices with API gateway template previewMicroservices with API gateway

    Clients behind an API gateway, services that each own their database, and an event bus for asynchronous work.

  • CQRS + event sourcing template previewCQRS + event sourcing

    Separate write and read paths: commands append events to an event store, projectors build read models for queries.

  • LLM application architecture template previewLLM application architecture

    Production building blocks around a model: gateway, guardrails, orchestrator, cache, vector DB, tools and observability.

  • LLM agent loop template previewLLM agent loop

    How a tool-using agent plans, calls tools, observes results and updates memory until the goal is met, with guardrails.

All solution architecture diagram templates · All templates

Use the event-driven architecture template