Quick Scoop

Amazon SQS, or Simple Queue Service , is a fully managed message queue in AWS that lets different parts of an application communicate asynchronously. It helps decouple services so one system can send work to a queue and another can process it later at its own pace.

What it does

  • Stores messages temporarily until a consumer is ready to process them.
  • Helps handle background jobs, retries, and traffic spikes without making your app slow or fragile.
  • Supports common distributed-system patterns, especially when you do not want services calling each other directly.

Simple example

Imagine an e-commerce site where checkout creates an order, but image resizing, email sending, and invoice generation happen later. The checkout service can put those tasks into SQS, and worker services can pull them when they are available.

Core ideas

  • Producer : sends a message to the queue.
  • Queue : holds the message durably.
  • Consumer : reads and processes the message.
  • Visibility timeout : hides a message briefly while one consumer is working on it, reducing duplicate processing.

Why people use it

SQS is useful when you want reliability, scalability, and loose coupling between services. It is especially common in microservices, serverless apps, and batch-processing workflows.

Queue types

  • Standard queues : high throughput and best-effort ordering.
  • FIFO queues : preserve strict order and help avoid duplicates in workflows that need sequencing.

TL;DR: SQS is AWS’s managed message queue for sending work between services reliably and asynchronously.