Back to blog

When is event-driven architecture the wrong answer?

Thắng Đoàn
Thắng Đoàn

You switched to events to decouple your services, and now nobody can trace why an order failed. That is not bad luck. It is the predictable cost of removing coupling without replacing it.

The coupling you removed comes back

Teams adopt the pattern for the decoupling while underestimating everything that replaces the coupling: schema governance, ordering assumptions, duplicate delivery, poison messages, and debugging across service boundaries. Event-driven architecture removes direct calls between services. Per The Augmented Dev, the producer no longer knows or cares who consumes its events. That is the win. But doshidhruv.com notes teams adopt the pattern for the decoupling while underestimating everything that replaces the coupling: schema governance, ordering assumptions, duplicate delivery, poison messages, and debugging across service boundaries. If you have no one owning schemas, EDA is the wrong answer for you today.

Debugging is the first thing to break

Code Opinion relays a team's verdict: "We switched to event driven architecture. Now we can't debug anything." He argues the pain was real but caused by how they understood and applied the pattern, not by the pattern itself. MoldStud reports the same operational side: bottlenecks and single points of failure can severely disrupt operations. If your team cannot answer what happened to a request, EDA will make that harder, not easier.

  • Correlation IDs on every event, so one request traces end to end
  • A central log of what each consumer did and when
  • A rehearsed answer to: what did this event trigger?

One label hides three patterns

Three different patterns hide under "we publish events": notification, state transfer, and event sourcing. Per doshidhruv.com, three different patterns hide under "we publish events": notification, state transfer, and event sourcing. Notification keeps events tiny but the consumer must call back to the source for details. That reintroduces temporal coupling, because the producer's API must still be up. Decide the style deliberately before your first production event, or the confusion will land on EDA's head.

  • Notification: something happened, consumer calls back for details
  • State transfer: the event carries the data itself
  • Sourcing: the event log is the source of truth

Speed is not a reason to switch

Teams stream events faster, not smarter. Forbes Councils members warn that teams stream events faster, not smarter, and that excitement over real-time capability needs thoughtful planning and guardrails. Hookdeck makes the same point structurally: moving from synchronous APIs to events and webhooks requires being grounded in messaging fundamentals first. If your domain needs a single immediate answer, like a payment authorization, request-response remains the honest model.

What this does not solve

None of the sources claim EDA fixes consistency. Duplicate delivery, ordering, and poison messages remain your job, per doshidhruv.com and Hookdeck. MoldStud adds that regular monitoring and performance analysis are still required to find bottlenecks. EDA moves work. It does not delete it.

If an order failed yesterday, could your team reconstruct the full event chain in under an hour?
Which of your service calls are conversations needing an answer, versus announcements nobody must reply to?

List your five most critical service interactions and mark each as conversation or announcement.

Sources

MoldStud: Common Mistakes in Event-Driven Architecture

Forbes: Event-Driven Architecture Pitfalls and Drawbacks

Code Opinion: 5 Event Driven Architecture Problems

doshidhruv.com: EDA Pitfalls and How to Avoid Them

Hookdeck: EDA Fundamentals and Common Pitfalls

The Augmented Dev: EDA Patterns and Pitfalls

Share:

Recommended for you

Enjoyed this article?

Subscribe for new articles. No spam. Unsubscribe anytime.

By subscribing you agree to receive the newsletter. No spam, and you can unsubscribe anytime.