Amazon Simple Queue Service: Difference between revisions

Revision as of 22:49, 14 November 2016

Revision as of 17:18, 17 November 2016

Line 39:

Amazon SQS guarantees '''at-least-once delivery'''. Messages are stored on multiple servers for redundancy and to ensure availability. If a message is delivered while a server is not available, it may not be removed from that server's queue and may be resent. {{As of|2007}}, Amazon SQS does not guarantee that the recipient will receive the messages in the order they were sent by the sender. If message ordering is important, it is required that the application place sequencing information within the messages to allow for reordering after 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<ref>[https://forums.aws.amazon.com/ann.jspa?annID=710] {{waybackwebarchive |url=https://web.archive.org/web/20110829121354/https://forums.aws.amazon.com/ann.jspa?annID=710 |date=20110829121354August 29, 2011 }}</ref> and then 256KB on 2013-06-18.<ref>{{cite web|url=http://aws.amazon.com/about-aws/whats-new/2013/06/18/amazon-sqs-announces-256KB-large-payloads/ |title=Amazon SQS and SNS Announce 256KB Large Payloads |publisher=Aws.amazon.com |date=2013-06-18 |accessdate=2015-08-13}}</ref> 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 (computer programming)|pointer]] to the data transmitted in the SQS message. Amazon has made an Extended Client Library available for this purpose [https://github.com/awslabs/amazon-sqs-java-extended-client-lib].

The service supports both unlimited queues and message traffic.