Events are foundational building blocks in modern integration architectures, and they can be transferred and published with the support of event brokers like Apache Kafka. Business events flow between components to exchange information. These events should be used like any other API, and therefore, they should be designed corresponding to the API-first principle as it is applied to synchronous APIs such as RESTful HTTP APIs.
Although this requirement is obvious, specification languages for designing APIs like AsyncAPI are not widely adopted. AsyncAPI is an open-source specification that provides a common language for defining and documenting asynchronous APIs, similar to how OpenAPI (Swagger) works for REST APIs.
Join this session to understand an end-to-end approach, which can be used to design events based on event storming and context maps using AsyncAPI. Additionally, we'll show how modern LLM tools can support the process even further.

Session outline:
1. AsyncAPI – a specification language for events and messages
2. An example with event storming
3. Definition of events out of a context map
4. Definition of the payloads
5. Message or event – that's the question
6. Checklist when and where events can be applied

The audience would come out of the session armed with the knowledge of how to use AsyncAPIs while using Apache Kafka as the message exchange backbone. This session is targeted towards data streaming engineers, architects, and business analysts.