AWS SQS Case Study
Case Study: redBus
Before we understand SQS we need to know what is Message Queuing. Message queue is a service that is just like a database with a higher throughput and faster speeds. When they are used it feels like there is nothing in the way. Lets try to understand the below topology.
Producer sends the data to the queue, consumer keeps going to the queue to check if there is any message for them and if they find any they download it.
Some examples include Rabbit MQ, Apache MQ, Active MQ, Kafka and Amazon SQS. Amazon SQS or Simple Queue Service is a Message Queuing Service that is completely managed by AWS. It allows data to be stored inside for 1 minute to 14 days! Using SQS you can send, store and receive messages between software components at any volume, without losing messages or requiring other services to be available.
Now that we know what is SQS, let us look at an industry use case.
Case Study: redBus
redBus is an Indian travel agency that specializes in bus travel all over India. Tickets are purchased through the company’s Website or through the Web services of its agents and partners.
The Challenge
It started with renting traditional datacenters. It faced problems with logistics and its biggest problem was that the infrastructure could not effectively handle processing fluctuations, which had a negative impact on its productivity.
Why Amazon Web Services
“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%.”
— Charan Padmaraju, Chief Technology Officer, redBus
The Benefits
The travel agency redBus is expanding their AWS solution to include Amazon SQS and SNS for monitoring, alerts, and intercommunication.
“Amazon SQS is an especially good solution for enabling messaging between external applications and our applications” — Padmaraju.
Source: redBus Case Study (amazon.com)
Feel free to contact on my LinkedIn.
