Abstract
Streaming applications are known for being scalable, resilient, and highly responsive, but building the event-driven architectures that power them is still a challenge for many developers. This challenge arises because event-driven architectures introduce new data models, protocols, and APIs that differ from traditional REST systems.
In this session, we will demonstrate how to bridge this gap using AsyncAPI to simplify the creation of event-driven streaming applications.
By using AsyncAPI specifications to describe Kafka topics and their interaction with HTTP APIs, we can abstract away the complexities of event-driven systems, enabling developers familiar with REST to seamlessly work with streaming applications.By using AsyncAPI 3.x HTTP Spec & Kafka Spec, we can map HTTP API endpoints to Kafka operations. We'll illustrate how HTTP requests, like creating or querying data, can trigger Kafka events and allow for seamless interaction between HTTP-based APIs and event-driven systems.
We'll dive into the request/response flow, showing how synchronous HTTP requests can be integrated with asynchronous Kafka topics for efficient communication in event-driven applications. Additionally, we'll emphasize the importance of using schemas for both HTTP requests and Kafka messages to maintain consistency and compatibility across services.
By the end of this session, you'll learn how to use AsyncAPI to connect HTTP APIs with Kafka topics, enabling seamless communication in event-driven applications. We'll also highlight the importance of using schemas to ensure consistency and compatibility between services.
