Event-driven architectures are not new - but the way they are used, documented, and specified has matured significantly in the past few years. Events often trigger the broader patterns of behavior that your service was built to deliver, or complete chains of behavior with asynchronous components, but event-driven services do not exist in a vacuum - or in mono-culture.

In today's talk, we will discuss the use of specifications to link event-driven elements to the behavior of the broader system and where focusing on maturing your approach to event-driven architecture has the greatest payoff for your organization and your team.