This document introduces Amazon SQS, a hosted message queuing service. It defines what a message queue is and why they are useful for distributed applications to provide reliability, scalability and loose coupling between services. Message queues allow services to communicate asynchronously. The document then discusses when message queues are needed, common options available, and provides an overview of Amazon SQS, including its core features like durability, availability and integration with AWS SDKs. It demonstrates the basic lifecycle of messages on SQS from a producer adding a message to a queue to a consumer processing it.

1. Presented By:
Yamini Bansal
Software Consultant
An Introduction to
Amazon SQS

2. Our Agenda
01 What is a messaging
queue?
02 When and Why we
need a messaging
queue?
03 Available options
04 Amazon SQS
05 Demo

3. Message Queue, what are they?

4. ● Mechanism for synchronous/asynchronous communication between
services.
● Mainly used for distributed applications.
● Help us decouple our services, provides reliability and scalability.
● Message persistence*.
Also known as “Message Broker”

5. Message Queue, when and why we need ‘em?

6. ● When we have a distributed application, the distributed components need to talk
to each other in a reliable manner.
● If during the communication, the recipient service gets down then what? Do we
lose the message?
When ?

7. ● We need message queue:
○ Reliability
○ Better performance
○ At-Least-Once delivery or Exactly-once delivery
○ Higher Throughput
Why ?

8. Available Options...
● There are two common implementations of message queue in UNIX are via:
○ SYS V API
○ POSIX
● Amazon SQS
● Apache ActiveMQ
● Apache kafka
● RabbitMQ
And many more...

9. Amazon SQS
● It offers secure, durable and available hosted queue that lets us integrate and
decouple distributed software systems and components.
● It provides a web services API and it can be accessed by any programming
language that AWS SDK supports.
● It supports both standard(supports at-least-once delivery) and FIFO(supports
exactly-once delivery) queues.
● Construct such as dead letter queues.

10. Life cycle of a Amazon SQS message
in a queue
● Component 1 -> send message -> Queue
● Queue -> message consumed by -> Component 2
● After processing message, either component 2 will delete it or it will be deleted
automatically by SQS.
Component 1 Component 2Queue
A A
Visibility Timer
Message Message

11. References
● https://docs.aws.amazon.com/AWSSimpleQueueService/latest/SQSDeveloperGuid
e/welcome.html
● https://docs.aws.amazon.com/AWSSimpleQueueService/latest/SQSDeveloperGuid
e/sqs-visibility-timeout.html
● https://docs.aws.amazon.com/AWSSimpleQueueService/latest/SQSDeveloperGuid
e/sqs-basic-architecture.html
● https://en.wikipedia.org/wiki/Message_queue

12. Thank You !
hello@knoldus.com www.knoldus.com
+(91) 1204287693@Knolspeak