> For the complete documentation index, see [llms.txt](https://docs.umbraco.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.umbraco.com/sustainability-best-practices/backend/async.md). # Async Utilizing asynchronous calls, often referred to as "fire and forget", presents substantial benefits from the perspective of sustainable systems design. By employing this approach, tasks are dispatched for execution without necessitating immediate waiting for their completion. This mechanism enhances system efficiency and responsiveness. It does it because it enables the system to continue processing other tasks while awaiting the completion of the asynchronous task. This strategy aligns closely with the principles of sustainable design by optimizing resource utilization. Rather than idling or blocking resources, the system can allocate them to other tasks, minimizing wastage and conserving energy. This proves especially advantageous in scenarios where processing times might vary or when tasks don't require immediate feedback. **Asynchronous** calls not only enhance overall system performance. They also contribute to a more ecologically conscious software ecosystem, where resource efficiency is a cornerstone of sustainable systems design. --- # 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.umbraco.com/sustainability-best-practices/backend/async.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.