2.1 Asynchronous Decoupling: SQS, FIFO & SNS Fanout

🎯 Key AWS SAA-C03 Architectural Takeaways

• Amazon SQS decouples producers from consumers; if processing takes longer than the Visibility Timeout, consumers will process duplicate copies of active messages.
• SQS FIFO queues guarantee strict order of delivery and exactly-once processing, using MessageGroupId for per-entity sequential ordering and cross-entity parallelism.
• The SNS Fanout pattern publishes messages to an SNS topic that replicates and pushes copies to multiple independent SQS queues for parallel microservice consumption.
• SQS Dead-Letter Queues (DLQs) with maxReceiveCount isolate corrupted poison pill messages after repeated worker failures, preventing infinite retry loops.

Decoupling components using message queues is fundamental to the AWS Reliability Pillar. Amazon SQS acts as a highly available, distributed buffer that absorbs traffic spikes and decouples producer systems from downstream consumer fleets. Producers push messages to SQS without concern for consumer availability or capacity, and workers pull messages at an optimal, controlled pace.

Understanding SQS Visibility Timeout is critical for long-running batch jobs. When a consumer receives a message, SQS starts the visibility timer (default 30 seconds), hiding the message from other workers. If the job takes 20 minutes and the visibility timeout is not extended, the timer expires and another worker retrieves the identical message. Applications must set visibility timeouts to exceed max processing times or programmatically call ChangeMessageVisibility during execution.

When strict ordering is mandatory, Amazon SQS FIFO queues deliver First-In-First-Out processing and exactly-once semantics. By assigning a MessageGroupId (such as customer account ID), messages within the same group are processed sequentially in strict order, while messages with different group IDs process concurrently across multiple workers.

To distribute events to multiple independent microservices, the SNS-to-SQS Fanout pattern publishes messages to an Amazon SNS topic subscribed by multiple SQS queues. Each subscriber receives a dedicated copy of the event, enabling independent retry policies, decoupled queue depths, and isolated processing logic without tight coupling.

⚠️ Common Pearson VUE / AWS Exam Traps

• Assuming SQS Standard queues guarantee order — Standard queues provide best-effort ordering; FIFO queues are required for strict sequential ordering.
• Allowing all microservices to read from a single shared SQS queue — one consumer will delete the message, starving all other downstream systems.
• Setting SQS Visibility Timeout lower than the maximum application processing duration, leading to duplicate processing storms.