> 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/monolithic-vs-service.md). # Monolithic vs. Service based Architecture When assessing the sustainability of architectural choices, the distinction between monolithic and service-based architectures takes center stage. **Monolithic architectures** encompass tightly integrated components within a single application, whereas **service-based architectures**, like microservices, emphasize modular, loosely coupled services. From a sustainable development perspective, **service-based architectures** hold a clear advantage. By allowing services to scale independently, microservices ensure efficient resource utilization. This agility translates into reduced energy consumption and optimal performance, as resources are allocated precisely where needed. **Monolithic architectures** often suffer from overprovisioning, which can lead to unnecessary resource usage and increased carbon footprint. In contrast, the ability of microservices to scale only the necessary components contributes to a more ecologically conscious approach. The service-based paradigm aligns closely with the principles of sustainable development. It does this by facilitating leaner resource consumption, promoting efficient scaling, and ultimately fostering a software ecosystem that operates in harmony with environmental preservation. --- # 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/monolithic-vs-service.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.