QuestionQ118

VerifiedDevelopment with AWS Services

A company has migrated an application to Amazon EC2 instances. Automatic scaling is working well for the application user interface. However, the process to deliver shipping requests to the company’s warehouse staff is encountering issues. Duplicate shipping requests are arriving, and some requests are lost or arrive out of order.

The company must avoid duplicate shipping requests and must process the requests in the order that the requests arrive. Requests are never more than 250 KB in size and take 5-10 minutes to process. A developer needs to rearchitect the application to improve the reliability of the delivery and processing of the requests.

What should the developer do to meet these requirements?

Explanation

SQS FIFO queues guarantee exactly-once delivery and strict message ordering, preventing duplicates and ensuring shipping requests process in arrival sequence. Coupling with Lambda event source mapping and a 5–10 minute processing window fits cleanly within FIFO throughput. Standard SQS (C) offers no ordering, Kinesis (A) lacks deduplication guarantees, and SNS (B) doesn't ensure order.

Learn more

Community Discussion

No comments yet. Be the first to start the discussion!