Amazon Simple Queue Service

Last updated
Amazon Simple Queue Service
Developer(s) Amazon.com
License Proprietary software
Website aws.amazon.com/sqs/

Amazon Simple Queue Service (Amazon SQS) is a distributed message queuing service introduced by Amazon.com as a beta in late 2004, and generally available in mid 2006. [1] [2]

Contents

API

Amazon provides SDKs in several programming languages, including: [3]

A Java Message Service (JMS) 1.1 client for Amazon SQS was released in December 2014.[ citation needed ]

Comparison with Other Messaging Systems

Amazon SQS FIFO and Azure Service Bus sessions are queue-based messaging systems that provide ordering guarantees within a message group or session attempt but do not necessarily guarantee ordered delivery in cases of retries or failures. In SQS FIFO, messages in the same message group are processed in order, with subsequent messages held until the preceding message is successfully processed or moved to the dead-letter queue (DLQ). Once a message is placed in the DLQ, it is no longer retried, creating a gap in the sequence. However, the remaining messages continue to be delivered in order. [4] [5] [6]

Azure Service Bus sessions function similarly by maintaining ordering within a session, provided a single consumer processes messages sequentially. The implementation differs from SQS FIFO but follows the same fundamental ordering principle. [7] [8]

In contrast, Apache Kafka is a distributed log-based messaging system that guarantees ordering within individual partitions rather than across the entire topic. Unlike queue-based systems, Kafka retains messages in a durable, append-only log, allowing multiple consumers to read at different offsets. Kafka uses manual offset management, giving consumers control over retries and failure handling. If a consumer fails to process a message, it can delay committing the offset, preventing further progress in that partition while other partitions remain unaffected. This partition-based design enables fault isolation and parallel processing while allowing ordering to be maintained within partitions, depending on consumer handling. [9]

Message delivery

Messages can be of any type, and the data contained within is not restricted. Message bodies were initially limited to 8KB in size but was later raised to 64KB on 2010-07-01 [10] and then 256KB on 2013-06-18. [11] For larger messages, the user has a few options to get around this limitation. A large message can be split into multiple segments that are sent separately, or the message data can be stored using Amazon Simple Storage Service (Amazon S3) or Amazon DynamoDB with just a pointer to the data transmitted in the SQS message. Amazon has made an Extended Client Library available for this purpose. [12]

The service supports both unlimited queues and message traffic.

Notable usage

Examples of companies that use SQS extensively include:

See also

References

  1. ↑ "Amazon Simple Queue Service Released". Amazon Web Services. 2006-07-13. Retrieved 2021-10-29.
  2. ↑ Barr, Jeff (2014-08-19). "My First 12 Years at Amazon.com". jeff-barr.com. Retrieved 2021-01-11.
  3. ↑ AWS (2024). "AWS SDKs and Tools" . Retrieved 2024-05-29.
  4. ↑ "FIFO queue delivery logic in Amazon SQS - Amazon Simple Queue Service". docs.aws.amazon.com. Retrieved 2025-03-22.
  5. ↑ "Using dead-letter queues in Amazon SQS - Amazon Simple Queue Service". docs.aws.amazon.com. Retrieved 2025-03-22.
  6. ↑ "Amazon SQS FIFO queues - Amazon Simple Queue Service". docs.aws.amazon.com. Retrieved 2025-03-22.
  7. ↑ spelluru (2025-03-21). "Azure Service Bus message sessions - Azure Service Bus". learn.microsoft.com. Retrieved 2025-03-22.
  8. ↑ spelluru (2025-02-07). "Service Bus dead-letter queues - Azure Service Bus". learn.microsoft.com. Retrieved 2025-03-22.
  9. ↑ Narkhede, Neha; Shapira, Gwen; Palino, Todd (2017). Kafka: the definitive guide: real-time data and stream processing at scale. Sebastopol, CA: O'Reilly Media. ISBN   978-1-4919-3616-0. OCLC   933521388.
  10. ↑ "Amazon SQS introduces Free Tier and adds Support for Larger Messages and Longer Retention". aws.amazon.com. 2010-07-01. Retrieved 2021-01-11.
  11. ↑ "Amazon SQS and SNS Announce 256KB Large Payloads". aws.amazon.com. 2013-06-18. Retrieved 2021-01-11.
  12. ↑ An extension to the Amazon SQS client that enables sending and receiving messages up to 2GB via Amazon S3. on GitHub
  13. ↑ Amazon Web Services (2014-11-14). AWS re:Invent 2014 | (PFC308) How Dropbox Scales Massive Workloads Using Amazon SQS . Retrieved 2024-12-07– via YouTube.
  14. ↑ Granqvist, Hans (2011-04-18). ""More Like This…" Building a network of similarity". Netflix Tech Blog. Archived from the original on 2016-11-28.
  15. ↑ Fang, Wenbin (2014-08-13). "Nextdoor Taskworker: Simple, Efficient & Scalable". Nextdoor Engineering.
  16. ↑ "Amazon SQS FAQs | Message Queuing Service | AWS". Amazon Web Services, Inc. Retrieved 2024-12-07.
This page is based on this Wikipedia article
Text is available under the CC BY-SA 4.0 license; additional terms may apply.
Images, videos and audio are available under their respective licenses.