Module 13

In this topology, the amount of requests to the backend can create a bottleneck of requests this crashing the servers. This is called Tight Coupling (three tier arhitecture)

  • We want to decouple this architecture to loosen it up so nothing gets bottlenecked

Loosen like ur ...

Amazon Simple Queue Service (SQS)

  • Is a fully managed message queueing service

  • Helps integrate and decouple distributed software systems and application components

  • Provides highly available, secure, and durable message-queueing capabilities

  • Provides an AWS Management Console interface and a web services API

Wilmer said "remember for the exam"

  • Visibility Timeout: After sending the first 5 messages(user-defined), it won't take requests from any other consumer for 30 seconds(user-defined)

  • Max message size: 256kb - only sending metadata

SQS Components

Example:

Queue types

Standard Queue

  • At-least-once delivery

  • Best-effort ordering

  • Nearly unlimited throughput

First in First Out (FIFO)

  • Exactly once processing

  • High throughput

SQS Operations

Amazon Simple Notification Service (SNS)

  • Is a fully managed pub/sub messaging service

  • Helps decouple applications through notifications

  • Provides highly scalable, secure, and cost-effective notification capabilities

  • Provides an AWS Management Console interface and a web services API

Types of SNS Subscribers

Example:

SNS and SQS Differences

SNS
SQS

Publisher -> Subcriber

Producer -> Consumer

One to many

One to one

Push (passive)

Pull (active)

Message persistence: NO

Message persistence: YES

Amazon MQ is a message broker service

PreviousModule 12NextModule 14

Last updated

Was this helpful?