"Everything looks like a red thumb when you're holding a golden hammer." Events are a part of a greater whole. It's a tool that you can use to solve certain da

"Everything looks like a red thumb when you're holding a golden hammer." Events are a part of a greater whole. It's a tool that you can use to solve certain data flows, but not all data flows. When you start taking more liberty with the word "eventually," you are almost certainly in a realm where event-driven makes the most sense. CQRS is a pretty good example of using many architectures (including event-driven) under a single greater architectural umbrella, and the thought patterns it introduces you to are incredibly useful. But no architecture is gospel, not even close. Any "pure" architecture is the tail wagging the dog. The problem comes first, the solution comes second, the architecture comes third.