We tend to overcomplicate things especially when we learn them. Your friend comes back from a conference with shiny new ideas and the next day you wake up with event driven architecture for communication, event sourcing for persistence, domain driven concepts scattered randomly on your sources and a distributed monolith in a monorepo. And none of this helps, quite the contrary. Since this is usually where I help companies, I’d like to show you a few recurring patterns of overcomplication and how to avoid them. I’m going to talk about:
when NOT to use an event bus and when it pays off,
why an in-memory events bus is useful mostly in Minecraft / Excel / Totalcmd,
how we steal concept and reuse them badly, thus making our lives harder
where 3 layered architecture is an antipattern, and why we came up with vertical slices and a few more things
