AWS SQS
AWS SQS
What is Amazon Simple Queue Service?
A hosted queue that is safe, long-lasting, and available through Amazon Simple Queue Service (Amazon SQS) permits the integration and decoupling of distributed software systems and components.
Dead-letter queues and cost allocation tags are two examples of common constructions available in Amazon SQS.
It offers a standard web services API that can be accessed with any programming language supported by the AWS SDK.
Benefits of using Amazon SQS:
Security: An Amazon SQS queue is yours to control who can send and receive messages.
Either custom SSE keys managed by AWS Key Management Service (AWS KMS) or the default server-side encryption (SSE) that is managed by Amazon SQS can be used to protect messages in queues when transmitting sensitive data.
Durability: Amazon SQS stores your messages on multiple servers to ensure their security.
At least once message delivery is supported by standard queues, while exact-once message processing and high-throughput mode are supported by FIFO queues.
Accessibility — Amazon SQS utilizes a repetitive foundation to give exceptionally simultaneous admittance to messages and high accessibility for creating and consuming messages.
Scalability:
Without any provisioning instructions, Amazon SQS can scale transparently to handle any load increases or spikes by processing each buffered request independently.
Reliability:
Amazon SQS locks your messages while they are being processed so that multiple producers and consumers can simultaneously send and receive messages.
Get Chithamparam’s stories in your inbox
Join Medium for free to get updates from this writer.
Customization: Your queues do not have to be identical; for instance, you can set a queue’s default delay.
Amazon SQS holds a pointer to the Amazon S3 object, and you can split a large message into smaller messages or store the contents of messages larger than 256 KB in either Amazon DynamoDB or Amazon Simple Storage Service (Amazon S3).
Amazon SQS Standard queues:
Standard is the default queue type provided by Amazon SQS.
The number of API calls that can be made per API action (SendMessage, ReceiveMessage, or DeleteMessage) supported by standard queues is nearly infinite.
Delivery of messages at least once is supported by standard queues.
However, due to the highly distributed architecture’s nearly limitless throughput, multiple copies of a message may occasionally be delivered out of order.
Best-effort ordering is provided by standard queues, ensuring that messages are typically delivered in the same order they were sent.
See Create a queue (console) for instructions on how to use the Amazon SQS console to create and configure queues.
See Amazon SQS Java SDK examples for Java examples.
As long as your application can process messages that arrive multiple times and are out of order, you can use standard message queues in many situations:
Allow users to upload media while resizing or encoding it, separating live user requests from extensive background work.
Process a large number of credit card validation requests by assigning tasks to multiple worker nodes.
Schedule the addition of multiple entries to a database with batch messages for future processing.
For quantities connected with standard lines, see Shares connected with lines.
See Recommendations for Amazon SQS standard and FIFO queues for best practices when working with standard queues.
