Events fundamentally change the way we build systems. As a means of communication they loosely couple microservices together, meaning sections of an architecture become isolated from the failure semantics of the rest. As a data model they tie communication and storage together via a technique called event sourcing, which retains information exactly as it happened, primed for future use cases or for analytics. Events also imply motion: Data moves from one application to another, with stream processors used to manipulate these data flows as they progress. Finally, events are the backbone of serverless architectures. A programming model that is likely to be prevalent in our future.
In this talk, we’ll look at the relationship between these different aspects of the humble event, providing insight into why the paradigm is important now, as well as reflecting on its inevitable positioning in our future.