Member-only story

4 Common Mistakes in Event-Driven Systems

A brief exploration

The Bored Dev
Better Programming
8 min readOct 11, 2022

Photo by Anna Gru on Unsplash

In the last few years, the adoption of event-driven systems has seen a considerable increase among big companies. What are the main reasons behind this trend? Is it purely based on hype or are there any valid reasons to support the adoption of this architecture? From our perspective, the main reasons why many companies are following this path are:

Loose-Coupling Between Components

Having individual components that interact in an asynchronous manner through events achieves a low coupling. We can modify, deploy and operate these components independently at different times without problem; this is a huge benefit in terms of maintenance and productivity costs.

Fire and Forget Concept

This advantage is highly related to loose coupling, but we thought it was worth mentioning individually due to its importance. One of the greatest advantages of these systems is that an event can be fired and we don’t really care how and when this event gets processed, only if it persisted and became durable in the corresponding topic.

Once a type of event is sent to a topic, new consumers interested in the event can subscribe and start processing them. The producer won’t have to do any work at all to…

Create an account to read the full story.

The author made this story available to Medium members only.
If you’re new to Medium, create a new account to read this story on us.

Or, continue in mobile web

Already have an account? Sign in

Responses (5)

What are your thoughts?