# Monolithic vs. Service based Architecture **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: 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: ``` GET https://docs.umbraco.com/sustainability-best-practices/backend/monolithic-vs-service.md?ask= ``` The question should be specific, self-contained, and written in natural language. 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.