Producer and consumer responsibilities By David Boyne

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

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

Exposing too much information in your events

What information should we expose in our events? What patterns can help?

Understanding stream and discrete events

What is the difference between streaming and discrete events? How can you use them?

Internal vs External Events

Internal vs External events? Integration Events? Public language? What does it all mean?

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.

EDA Visuals: The book

Join over 13,000 others learning EDA and download all the EDA visuals directly to your computer.

This book contains all the visuals in one book, you can download, read offline and explore.

Purchase book $15.00

Purchasing the book supports my work, but for whatever reason if the book is beyond your budget, you can download it for free here.

Purchase book $15.00