A startup is designing a web application on AWS. They want to ensure that if the database layer experiences a temporary outage, the front-end web servers can still accept incoming customer orders without immediately failing. Which AWS Cloud design principle should the startup implement to achieve this goal?
- Loose couplingAnswer
- BTight coupling
- COver-provisioning
- DManual scaling
Answer
Loose coupling
Loose coupling is the correct design principle because it isolates components of an application (often using intermediary services like Amazon Simple Queue Service or Amazon EventBridge). This ensures that if one component (such as the database) becomes unavailable, other components (such as the web servers) can continue to function and accept requests without failing immediately.
Step-by-Step Solution
Key Concept
Loose coupling is a fundamental AWS design principle that decouples application components (e.g., using queues or asynchronous communication) so that they run independently. This prevents a failure in one service from cascading to other services, improving overall system resilience.