When you scale event driven architectures, your ability to keep the model of how you use events 'in your head' collapses and you need to move towards more formality in how you manage your events.

- How do you discover event APIs? Who publishes, who subscribes? What do the fields on the message mean?
- How do you gain an understanding of the flows of messages in your system for choreography?
- How do you manage the infrastructure associated with events such as topics, queues, access controls?
- How do you manage the versioning of events and ensure you do not break consumers?

In this session we will examine these questions and more. We will look at the use of emerging standards such as AsyncAPI and CloudEvents to document our event based APIs,  how they can help us generate code to manage the required infrastructure, how they can help us to understand the flow of events within our systems and how they can help us scaffold new applications. We will demo an end-to-end usage of AsyncAPI to define our APIs, scaffold the code required, and deploy the necessary infrastructure to run.