> 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.md).

# Backend

- [Backend Overview](https://docs.umbraco.com/sustainability-best-practices/backend/backend.md): Here you can find the Sustainability Best Practices with focus on backend techniques.
- [Upgrades and patches](https://docs.umbraco.com/sustainability-best-practices/backend/upgrades-and-patches.md): Implementing upgrades and patches, such as migrating to Umbraco 10+, is highly advantageous from the standpoint of sustainable system design.
- [Cache responses](https://docs.umbraco.com/sustainability-best-practices/backend/cache-responses.md)
- [Sustainable Design Patterns](https://docs.umbraco.com/sustainability-best-practices/backend/sustainable-design-patterns.md)
- [Performance Testing](https://docs.umbraco.com/sustainability-best-practices/backend/performance-testing.md): Conducting thorough performance testing and optimization of backend services holds great merit from the standpoint of sustainable system design.
- [Common pitfalls](https://docs.umbraco.com/sustainability-best-practices/backend/common-pitfalls.md): Tackling common pitfalls in implementing an Umbraco solution is integral within the realm of sustainable system design.
- [SOAP, REST and GraphQL](https://docs.umbraco.com/sustainability-best-practices/backend/soap-rest-graphql.md): Viewing APIs through the lens of sustainable development reveals crucial considerations for optimizing their efficiency.
- [SQL optimization](https://docs.umbraco.com/sustainability-best-practices/backend/sql-optimization.md): Efficient SQL optimization, particularly in the precise utilization of joins, carries significance within the framework of sustainable system design.
- [JAMstack](https://docs.umbraco.com/sustainability-best-practices/backend/jamstack.md): The adoption of JAMstack architecture, Static Site Generation (SSG), and Content Delivery Network (CDN) distribution stands as a commendable choice for sustainable system design.
- [Monolithic vs. Service based Architecture](https://docs.umbraco.com/sustainability-best-practices/backend/monolithic-vs-service.md): When assessing the sustainability of architectural choices, the distinction between monolithic and service-based architectures takes center stage.
- [Async](https://docs.umbraco.com/sustainability-best-practices/backend/async.md): Utilizing asynchronous calls, often referred to as "fire and forget", presents substantial benefits from the perspective of sustainable systems design.
- [Background tasks](https://docs.umbraco.com/sustainability-best-practices/backend/background-tasks.md): Implementing background tasks or batching up requests to run in sustainable cloud regions and during off-peak hours of power consumption is a commendable sustainable system design practice.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.umbraco.com/sustainability-best-practices/backend.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.