> 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/a/asynchronous-operation.md). # Asynchronous Operation Operations that occur without waiting for the previous operation to complete, improving efficiency and performance. An asynchronous operation is a task that executes independently of the main program flow, allowing the system to continue processing other work while waiting for the operation to complete. Unlike synchronous operations, which block execution until they finish, asynchronous operations return control immediately and notify the caller when the result is ready. Asynchronous patterns are essential in web development and API design, particularly for I/O-bound tasks like database queries, HTTP requests to external services, and file operations. Common implementation mechanisms include callbacks, promises, and async/await syntax in languages like JavaScript and Python. In serverless and API gateway contexts, asynchronous processing is valuable for handling long-running tasks. Instead of keeping a client connection open, the API can accept a request, place the work on a queue, and return an immediate acknowledgment. The client can then poll for results or receive a webhook notification when processing completes. This approach improves responsiveness and resource utilization. --- # 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/a/asynchronous-operation.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.