Understanding what Event-Driven Architecture is all about and how AsyncAPI is building the future of EDA's

Legend has it that you can only interact with web services using REST APIs. The same legend also has it that HTTP is the only way of communication on the interweb. And I am here to bust this myth by introducing you to EDA and a community whose mission is to build the future of EDA.

Request-response is the traditional communication pattern used in computing and in most web applications. In web services, the standard approach is for a client to make a synchronous HTTP request, and then wait for a response from the webserver. In a microservices architecture, request-response is also commonly used: a web server sends a connection request or query to a database, then waits for a response. For many use cases, this pattern — a chain of synchronous requests and responses — works well. Until it doesn’t.

What happens when one link in the chain goes down? Requests that are waiting for a response don’t receive one at all. They continue to wait, or they time out. The entire application is blocked. What’s more, as the number of services increases, the number of synchronous interactions between them increases as well. In such a situation, a single system’s downtime affects the availability of other systems as well.

In this session, I’m going to introduce you to the world of Event-Driven Architecture and how it helps solve the problem above. Thank you in advance.