An insurance firm is migrating its claims processing system to AWS. The system consists of a web portal, a document generation service, and a document archiving service. Currently, the web portal calls the document generation and archiving services synchronously. If the archiving service is temporarily unavailable, the entire claim submission fails. How should the firm redesign the application on AWS to resolve this issue?
- AConsolidate the web portal, document generation, and document archiving services into a single monolithic application deployed on a single Amazon EC2 instance.
- BIncrease the size of the web portal's Amazon EC2 instances to handle the additional connection load and wait times when downstream services fail.
- Redesign the system to communicate asynchronously using Amazon Simple Queue Service (Amazon SQS), decoupling the web portal from downstream processing.Answer
- DConfigure the web portal to trigger synchronous execution of all services inside a single database transaction across multiple Availability Zones.
Answer
Redesign the system to communicate asynchronously using Amazon Simple Queue Service (Amazon SQS), decoupling the web portal from downstream processing.
Decoupling components using an asynchronous message queue like Amazon Simple Queue Service (Amazon SQS) is a core AWS design principle (loose coupling). It allows the web portal to queue requests and continue responding to users even if downstream services (like document generation or archiving) are experiencing latency or are temporarily offline.
Step-by-Step Solution
Key Concept
Loose coupling
Estimated Time:1m 30s