Help Center/ Well-Architected Framework/ Well-Architected Framework and Practices/ Resilience Pillar/ Rapid Fault Recovery/ RES08 Dependency Reduction and Degradation/ RES08-02 Using Loose Coupling to Reduce Dependencies
Updated on 2025-05-22 GMT+08:00
View PDF
Share

RES08-02 Using Loose Coupling to Reduce Dependencies

If internal components of a system directly access each other, they become tightly coupled. The status change of one component directly affects other components, decreasing the availability of all components. A loosely coupled architecture minimizes dependencies between components. Each component can be changed or extended on its own without impacting others. This makes the system more adaptable, simpler to maintain, easier to upgrade, and highly dependable.

  • Risk level

    Medium

  • Key strategies
    • Use message queues, caches, and load balancers for component communication. These techniques make components loosely coupled and reduce the impacts of one component on others.
  • Related cloud services and tools
    • Elastic Load Balance (ELB)
    • Distributed Cache Service (DCS)
    • Distributed Message Service (DMS) for Kafka
    • Distributed Message Service (DMS) for RabbitMQ
    • Distributed Message Service (DMS) for RocketMQ
    • EventGrid (EG)