A company is designing a new microservices-based application on AWS. When an order is placed, the order details must be sent to two separate downstream systems: an inventory management service and a shipping coordination service. The orders must be processed by both services in the exact chronological sequence they were placed. Which combination of services should a solutions architect recommend to decouple these systems while preserving the message order? (Select TWO.)
- Amazon SQS FIFO queues to buffer messages for each downstream serviceAnswer
- Amazon SNS FIFO topics to fan out the messages to the queuesAnswer
- CAmazon SQS Standard queues to queue messages for each downstream service
- DAmazon RDS Read Replicas to replicate the order database for downstream services
- EAmazon Route 53 Latency Routing to route messages to the closest downstream service
Answer
Amazon SQS FIFO queues and Amazon SNS FIFO topics are the correct services to decouple the components and preserve the message order.
To decouple microservices while ensuring that messages are sent to multiple endpoints (fan-out) and processed in the exact chronological sequence, Amazon SNS FIFO topics and Amazon SQS FIFO queues must be used in combination. SNS FIFO topics manage ordering during distribution, and SQS FIFO queues ensure that consumers pull messages in the correct sequence.
Step-by-Step Solution
Key Concept
Decoupling message-driven architectures while preserving strict message ordering using SNS and SQS FIFO configurations.
Estimated Time:1m 30s