Hacker News new | ask | show | jobs
by worik 747 days ago
"Event driven architecture ". Mēh!

There is no avoiding it when dealing with, erm, events.

Events are things that happen that you cannot predict exactly when, where, and what.

The user clicked the mouse

The wind changed direction

Using Events to signal state change from one part of a system to another is a bad idea. Use a function call.

A rule of thumb is if the producer and the consu,er are in the same system then "Event Driven Architecture " is the anti pattern

1 comments

What if one event should trigger many actions?