Re:Beware anti patterns in event driven architecture
by tadfisher on Saturday June 08, 2024 @07:26PM
(#40620841)
I think the true term for this phenomenon is "decoherence" rather than "decoupling". Your components are still as coupled as they ever were, but the coupling has moved from compile-time (e.g. function calls) to runtime. The component that "handles events" decoheres the entire system because it's now responsible for the entire messaging layer between components, rather than the individual components being responsible for their slice of the system.
[ Parent
| on HN ]
Re:Beware anti patterns in event driven architecture
by jesse__ on Monday June 10, 2024 @12:03AM
(#40630020)
That's a great name for that property. I've always cringed when people say 'something something decoupling' because most of the time the end result is actually just as coupled, but ends up indirected or something. Now I have a more specific word for it, thanks!!