Good and hard parts of EDA By David Boyne
Good and hard parts of EDA By David Boyne
Good parts
-
Flexibility - The ability for consumers to come and go without impacting the producer. When new business requirements occur, existing events can be listening too and consumers can be created.
-
Process in real time - Some systems can allow for events to be processed in real-time or near-real time. Thinking about the user experience, could this lead to a better UX?
-
Fault tolerance - Consumers are decoupled by nature, if a consumer was to break or fail to process the event, the failure is isolated to that consumer.
Hard parts
Things to think about.
-
Error Handling - When errors occur, being able to track the error and understand what is going on. Need to consider DLQ or ways to capture events before they are gone forever… if that’s important to you.
-
Debugging - Producers and consumers are distributed by design, so being able to trace and debug can be hard.
-
Idempotency - Key to think about idempotency. If the same event was to be replayed into your consumer, what will happen? Avoid side effects, have the same outcome if event replays were to happen.
Explore other visuals
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 13,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.