How does Simple Queue Service from AWS works

Reading Time: 3 minutes

Introduction:-

SQS (Simple Queue Service) is a platform for pull notifications. A message queue that stores messages awaiting processing is accessible through the web service SQS. It also provides a dependable, highly scalable hosted queue for storing messages between servers.

SQS is a quick, dependable, and fully managed message queue service.

You can do away with the hassle of maintaining a highly available message cluster by using an SQS. Without destroying the SQS queue itself, you can remove every message from it.

Standard Queue:-

High Throughput (Unlimited).
a minimum of one delivery.
Duplication is conceivable.
the best possible order.

FIFO Queue:-

Constrained Throughput (300 TPS)
One processing only
No duplication is possible.
FIFO queues with strict ordering and only allowed to process 300 transactions per second (TPS)

Types of Polling:-

Short Polling:–

Even if the queue is empty there is a response to a request.
It doesn’t hold off till the message comes up in the queue.
It just looks up a portion of the servers that are open for communication Default by SQS
The Receive Wait Time setting is 0.

Long Polling:-

Firstly , Long Polling is referred to as regular/short polling. it use lesser requests and request costs by:-

Removing erroneous empty responses search on all other server amazon
SQS has been altered such that responses won’t be delivered until the message is no longer in the queue and unless the connection times out in an effort to decrease the frequency of empty responses (20 seconds).
The receive message wait time is set to a maximum of 20 seconds and is specified to be non-zero.
The cost for both pollings is the same.

SQS Pricing:-

The first 1,000,000 monthly requests are free, and then the cost varies by area.

For eg ->

Regular line: $040 per million requests

FIFO queue – request for $050 million

_{How Amazon SQS Charges:}

Firstly, Every Amazon SQS action counts as an API action.
Secondly, FIFO Request: FIFO rates apply to any API activity that involves sending, receiving, deleting, or altering the visibility of messages from FIFO queues.
Thirdly, Request Content: A single request may contain one to ten messages.
Lastly, Size of Payload: For every 64 kb chunk, a payload and one resource are charged.