The dark side of events

Events are our industrys near and dear. All technological conferences are full of talks on event sourcing, event-driven architectures, or event-driven integrations. Vladik Khononov adds another one, but a bit different. Lets talk about the dark side of this patternthe cases in which events turn into an anti-pattern, how to identify them, and, of course, how to turn the project around.

Events are our industry’s near and dear. All technological conferences are full of talks on event sourcing, event-driven architectures, or event driven integrations. So, hey, why not make another one? But a bit different: let’s talk about the dark side of this pattern. Events, as any tool, can be used productively or destructively. During the last eight years, Internovus found so many creative ways to do the latter: the different ways events can introduce coupling so strong it make the classic enterprise monolith envious, multiple ways of using events to introduce accidental complexity, how to use events to turn a microservice into an architectural Trojan horse, and why some events, just like underwear, are better kept private. Those insights aren’t for the faint of heart, but fear not. You’ll get heuristics to help you identify those situations, eliminate event-driven accidental complexities, and make events great again.