Amazon SQS Feature and Use-Case in Industry

Possible use cases for Amazon SQS or any Queue Service

  • Any component of an application can later retrieve the messages programmatically using the Amazon SQS API.
  • Amazon SQS is a distributed queue system that enables web service applications to quickly and reliably queue messages that one component in the application generates to be consumed by another component where a queue is a temporary repository for messages that are awaiting processing.

Amazon SQS offers two queue types for different application requirements:

  1. Standard Queues
  • At-Least-Once Delivery: A message is delivered at least once, but occasionally more than one copy of a message is delivered.
  • Best-Effort Ordering: Occasionally, messages might be delivered in an order different from which they were sent.
fig 1: Standard Queue
fig 2: FIFO Queue
  • First-In-First-Out Delivery: The order in which messages are sent and received is strictly preserved (i.e. First-In-First-Out).
  • High Throughput: If you use batching, FIFO queues support up to 3,000 transactions per second, per API method (SendMessageBatch, ReceiveMessage, or DeleteMessageBatch). The 3000 transactions represent 300 API calls, each with a batch of 10 messages. To request a quota increase, submit a support request. Without batching, FIFO queues support up to 300 API calls per second, per API method (SendMessage ,RecieveMessage, or DeleteMessage).

Amazon SQS visibility timeout

When a consumer receives and processes a message from a queue, the message remains in the queue. Amazon SQS doesn’t automatically delete the message. Because Amazon SQS is a distributed system, there’s no guarantee that the consumer actually receives the message(eg:due to a connectivity issue,consumer application or anything else)Thus, the consumer must delete the message from the queue after receiving and processing it.

What about RabbitMQ??

fig 3 : Image of RabbitMQ

BMW Case Study

fig 4 : Logo of BWM

RedBus Case Study

fig 5: Redbus logo
  • Why Amazon Web Services: After testing the AWS solution on a small application for several months, the travel agency determined that it was very workable and convenient. Although redBus was quite enthusiastic about the on-demand instances and variety of instance types, several other features cemented the company’s decision to migrate completely to AWS. These features included the ability to easily manage access to servers through security groups, the easy-to-use, self-service management console, the concept of Elastic IPs, and superior support.
  • Its Benefits: Since migrating to AWS, redBus has seen measurable improvements in the bottom line. Padmaraju says, “By scaling up and down dynamically based on the load, we maintain performance as well as minimize cost. With the time savings that the IT and development staffs obtain from the AWS solution, AWS gives us an overall cost benefit of about 30–40%.” He adds, “By hosting at [the AWS Asia Pacific (Singapore) region], redBus.in gained significantly in terms of website performance by way of reduced latency (about 4x). This is a great advantage when the customers are from India.”

RHEL8 | AWS | Ansible | Docker| K8s | Jenkins