Sustainability Best Practices
CMSCloudHeartcoreDXP
  • Introduction
  • Infrastructure
    • Infrastructure Overview
    • Hosting
    • Architecture
    • Security and Bots
  • Backend
    • Backend Overview
    • Upgrades and patches
    • Cache responses
    • Sustainable Design Patterns
    • Performance Testing
    • Common pitfalls
    • SOAP, REST and GraphQL
    • SQL optimization
    • JAMstack
    • Monolithic vs. Service based Architecture
    • Async
    • Background tasks
  • Frontend
    • Frontend Overview
    • Page weight budget
    • Image optimization
    • Asset optimization
    • Limit use of 3rd parties
    • Lazyload resources
    • Mobile first
  • Editor
    • Editor Overview
    • Content Types
    • Content Optimization
    • Design Choices
    • Data Management
    • Housekeeping
  • Telemetry
    • Telemetry Overview
    • February 2024
Powered by GitBook
On this page

Was this helpful?

Edit on GitHub
Export as PDF
  1. Backend

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.

PreviousJAMstackNextAsync

Last updated 1 year ago

Was this helpful?