Amazon Simple Queue Service: Difference between revisions

Revision as of 03:37, 30 December 2020

Revision as of 17:13, 11 January 2021

Line 5:

| developer = [[Amazon.com]]

| license = [[Proprietary software]]

| website = {{URL|httphttps://aws.amazon.com/sqs/}}

}}

'''Amazon Simple Queue Service''' ('''Amazon SQS''') is a distributed [[message queuing service]] introduced by [[Amazon.com]] in late 2004.<ref>{{cite web|url=http://jeff-barr.com/2014/08/19/my-first-12-years-at-amazon-dot-com/ |title=JeffMy Barr'sFirst Blog12 Years at Amazon.com|publisherfirst=Jeff|last=Barr|date=2014-08-19|website=jeff-barr.com |access-date=20152021-0801-1311}}</ref> It supports programmatic sending of messages via web service applications as a way to communicate over the Internet. SQS is intended to provide a highly scalable hosted [[message queue]] that resolves issues arising from the common [[producer-consumer problem]] or connectivity between producer and consumer.

Amazon SQS can be described as [[commoditization]] of the messaging service. Well-known examples of messaging service technologies include [[IBM WebSphere MQ]] and [[Microsoft Message Queuing]]. Unlike these technologies, users do not need to maintain their own server. Amazon does it for them and sells the SQS service at a per-use rate.

Line 16:

==Authentication==

Amazon SQS provides authentication procedures to allow for secure handling of data. Amazon uses its [[Amazon Web Services]] (AWS) identification to do this, requiring users to have an AWS enabled account with [[Amazon.com; this can be created at [http://aws.amazon.com Amazon Web Services (AWS) - Cloud Computing Services]]. AWS assigns a pair of related identifiers, your AWS access keys, to an AWS enabled account to perform identification. The first identifier is a public 20-character Access Key. This key is included in an AWS service request to identify the user. If the user is not using [[SOAP (protocol)]] with [[WS-Security]], a digital signature is calculated using the Secret Access Key. The Secret Access Key is a 40-character private identifier. AWS uses the Access Key ID provided in a service request to look up an account's Secret Access Key. Amazon.com then calculates a digital signature with the key. If they match then the user is considered authentic, if not then the authentication fails and the request is not processed.

==Message delivery==

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>{{Cite web|url=https://forums.aws.amazon.com/ann.jspa?annID=710|archiveabout-url=https:aws/whats-new/web.archive.org2010/web07/2011082912135401/https://forums.aws.amazon.com-sqs-introduces-free-tier-and-adds-support-for-larger-messages-and-longer-retention/ann.jspa?annID=710|url-status=dead|title=AWS Developer Forums: Amazon SQS introduces Free Tier and adds supportSupport for Larger Messages and Longer Retention|archive-date=August 29, 20112010-07-01|website=forums.aws.amazon.com|access-date=2021-01-11}}</ref> and then 256KB on 2013-06-18.<ref>{{cite web|url=httphttps://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 |publisherwebsite=Awsaws.amazon.com |date=2013-06-18 |access-date=20152021-0801-1311}}</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/<ref>{{GitHub|awslabs/amazon-sqs-java-extended-client-lib |An extension to the Amazon SQS client that enables sending and receiving messages up to 2GB via Amazon S3. : awslabs}}</amazon-sqs-java-extended-client-lib].ref>

The service supports both unlimited queues and message traffic.

Line 33:

==Notable usage==

[[Dropbox (service)|Dropbox]], [[Netflix]]<ref>{{Cite web

[[Dropbox (service)|Dropbox]], [[Netflix]]<ref>{{Cite web|url=http://techblog.netflix.com/2011/04/more-like-this-building-network-of.html|title=Netflix TechBlog – Medium|website=Medium}}</ref> and [[Nextdoor]]<ref>{{Cite web|url=https://engblog.nextdoor.com/nextdoor-taskworker-simple-efficient-amp-scalable-ac4f7886957b|title=Nextdoor Taskworker: Simple, Efficient &amp; Scalable|first=Wenbin|last=Fang|date=August 13, 2014|website=Nextdoor Engineering}}</ref> are examples of companies that use SQS extensively. SQS is also widely used within Amazon.com.

| url=http://techblog.netflix.com/2011/04/more-like-this-building-network-of.html

| title=“More Like This…” Building a network of similarity

| date = 2011-0704-0818

| first=Hans

| last=Granqvist

| work=Netflix Tech Blog

| archive-url=https://web.archive.org/web/20161128083030/http://techblog.netflix.com/2011/04/more-like-this-building-network-of.html

| archive-date=2016-11-28

| url-status=dead}}</ref> and [[Nextdoor]]<ref>{{Cite web

| url=https://engblog.nextdoor.com/nextdoor-taskworker-simple-efficient-amp-scalable-ac4f7886957b

| title=Nextdoor Taskworker: Simple, Efficient &amp; Scalable

| first=Wenbin

| last=Fang

| date=August 13, 2014

| website=Nextdoor Engineering}}</ref> are examples of companies that use SQS extensively. SQS is also widely used within Amazon.com.

==Pricing==

Line 87 ⟶ 102:

==See also==

* [[Java Message Service]]

* [[IronMQ]]

* [[Message queue]]

* [[Message Queuing as a Service]]

Line 95 ⟶ 109:

==References==

{{Reflist}}

==External links==

*[https://www.amazon.com/Simple-Queue-Service-home-page/b?node=13584001 Amazon Simple Queue Service homepage]

*[https://github.com/adamw/elasticmq ElasticMQ - replicated message queue implementing the Amazon SQS interface]

{{Refbegin}}

* {{cite web

| title = Amazon Simple Queue Service

| url = http://docs.amazonwebservices.com/AWSSimpleQueueService/latest/SQSGettingStartedGuide/

| date = 2011-07-08

}}

{{Refend}}

{{Cloud computing}}