> 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/sustainable-design-patterns.md). # Sustainable Design Patterns Sustainable design patterns are instrumental in crafting eco-conscious and efficient solutions. These patterns prioritize enduring efficiency, optimal resource utilization, and minimized negative impacts. A notable example is the "circuit break" pattern, which originates from software engineering but has far-reaching applications. Similar to an electrical circuit breaker that prevents surges, the circuit break design pattern enhances resilience by swiftly detecting and mitigating faults. This prevents wasteful resource usage during system failures and streamlines recovery. For an in-depth understanding of the circuit break pattern, you can explore Microsoft's Azure Architecture Patterns documentation. Integrating such sustainable patterns, whether through load balancing, refined database queries, or efficient caching, reduces energy consumption while improving system responsiveness. By incorporating these patterns, we pave the way for a sustainable digital landscape that coexists harmoniously with ecological considerations. --- # 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/sustainable-design-patterns.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.