> For the complete documentation index, see [llms.txt](https://docs.serverlessapigateway.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.serverlessapigateway.com/glossary/e/event-driven-architecture.md). # Event-Driven Architecture A software architecture paradigm promoting the production, detection, consumption of, and reaction to events. Event-Driven Architecture (EDA) is a software design pattern in which the flow of the program is determined by events -- significant changes in state or occurrences that the system detects and responds to. Components communicate by producing and consuming events rather than through direct request-response calls. In an event-driven system, event producers emit events to a message broker or event bus (such as Apache Kafka, AWS EventBridge, or RabbitMQ), and event consumers subscribe to and process events asynchronously. This decoupling allows components to evolve independently and improves system resilience, since a failure in one consumer does not block the producer. Event-driven patterns complement API gateway architectures. An API gateway can accept synchronous HTTP requests from clients and publish them as events for asynchronous processing by backend services. This hybrid approach provides a clean external API interface while leveraging the scalability and loose coupling of event-driven processing internally. Serverless functions are natural event consumers, triggered by messages on queues or topics. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.serverlessapigateway.com/glossary/e/event-driven-architecture.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.