SQS Benefits Summary (from Amazon)
-
Operational Efficiency - Eliminate Administrative Overhead
-
AWS manages the ongoing operations and underlying infrastructure needed to reliability run and scale.
-
Queues are dynamically created and scale automatically so you can build and grow applications quickly - and efficiently.
-
-
Reliability - Ensure Message Delivery
-
Can transmit any volume of data, at any level of throughput, without losing messages or requiring other services to be available.
-
Multiple copies of every message is stored redundantly across multiple availability zones.
-
Message delivery is at least once with standard queues, and exactly once with FIFO queues.
-
-
Security - Protect Sensitive Data
-
Can exchange sensitive data between applications using server-side encryption (SSE) to encrypt each message body.
-
Amazon SQS SSE integration with AWS Key Management Service (KMS) allows you to centrally manage the keys that protect SQS messages along with keys that protect your other AWS resources.
-
AWS KMS logs every use of your encryption keys to AWS CloudTrail to help meet your regulatory and compliance needs.
-
Authentication mechanisms also ensure that messages stored in Amazon SQS message queues are secured against unauthorized access.
-
-
Integration - Accelerate Application Development
-
Amazon SQS is deeply integrated with other AWS services.
-
Integrations include compute services such as EC2, ECS, and Lambda, as well as with storage and database services such as S3, RDS and DynamoDB.
-
SQS works with SNS to deliver a powerful messaging solution.
-
-
Scalability - Scale Elastically and Cost-Effectively
-
SQS leverages the AWS cloud to dynamically scale based on demand.
-
There is no limit to the number of messages per queue, and standard queues provide nearly unlimited throughput.
-
Costs are based on usage which provides significant cost saving versus the “always-on” model with self-managed messaging middleware.
-
-
Productivity - Get Started Quickly
-
Easy to get started with SQS using the simple console or SDK of your choice.
-
You can quickly add SQS to your code using only four APIs: CreateQueue, SendMessage, ReceiveMessage, and DeleteMessage.
-
The same API applies to both Standard Queues and FIFO Queues.
-
-
SQS Special use cases
-
Need to process messages with different priority.
-
You may have to create different queues for different priority.
-
-
Polling in tight cycles uses more CPU cycles (especially when no messages are coming).
-
Use long polling. Will have to poll only in 20 seconds when no messages. Will return immediately if there is a message.
-
References (Deprecated):
- heartin's blog
- Log in or register to post comments

Recent comments