Producer and consumer responsibilities By David Boyne

EDA visuals and the book is free thanks to our sponsors:

Serverless infrastructure for event-driven architecture.

Manage, secure, and govern every API in your organization.

Delivering Apache Kafka professional services to your business.

When building event-driven applications it’s important to know the responsibility of the consumer and producer. This diagram represents my thoughts on it, but I think from design to design it may differ.

Use this diagram as a base, but you may want to adapt it based on your architecture.

Explore other visuals

Message translator pattern

Translate messages into new formats, data types or even protocols. Use pattern to decouple through contracts.

Good and hard parts of EDA

Event sourcing and change data capture to for applications.

Content enricher pattern

Enrich data before it reaches downstream consumers

Want to work together?

If you're interested in collaborating, I offer consulting, training, and workshops. I can support you throughout your event-driven architecture journey, from design to implementation. Feel free to reach out to discuss how we can work together, or explore my services on EventCatalog.

Download EDA Visuals

Join over 10,000 others learning EDA and download all the EDA visuals directly to your computer. This document updates everytime a new visual is added so make sure you come back to get the latest.

Download now →