Why messaging services matter in AWS - Why It Works

Introduction

Messaging services help different parts of a system talk to each other without being directly connected. They solve the problem of making sure messages get delivered even if one part is busy or offline.

When you want to send notifications from one app to many users reliably.

When you need to connect different parts of your system that run separately and at different speeds.

When you want to make sure messages are not lost if a service crashes or restarts.

When you want to process tasks one by one without losing any requests.

When you want to scale parts of your system independently without breaking communication.

Commands

This command creates a new messaging queue named 'my-queue' in AWS SQS. It sets up a place where messages can be stored and retrieved later.

Terminal

aws sqs create-queue --queue-name my-queue

Expected Output

{"QueueUrl": "https://sqs.us-east-1.amazonaws.com/123456789012/my-queue"}

→

--queue-name - Specifies the name of the queue to create

This command sends a message with the text 'Hello from my app' to the queue we created. It shows how to put messages into the queue for other parts to read.

Terminal

aws sqs send-message --queue-url https://sqs.us-east-1.amazonaws.com/123456789012/my-queue --message-body "Hello from my app"

Expected Output

{"MD5OfMessageBody": "8b1a9953c4611296a827abf8c47804d7", "MessageId": "1234abcd-12ab-34cd-56ef-1234567890ab"}

→

--queue-url - Specifies the exact queue to send the message to

→

--message-body - The content of the message being sent

This command retrieves one message from the queue. It shows how a service can get messages to process them.

Terminal

aws sqs receive-message --queue-url https://sqs.us-east-1.amazonaws.com/123456789012/my-queue

Expected Output

{"Messages": [{"MessageId": "1234abcd-12ab-34cd-56ef-1234567890ab", "ReceiptHandle": "AQEBwJnKyrHigUMZj6rYigCgxlaS3SLy0a...", "MD5OfBody": "8b1a9953c4611296a827abf8c47804d7", "Body": "Hello from my app"}]}

→

--queue-url - Specifies the queue to receive messages from

This command deletes a message from the queue after it has been processed. It prevents the same message from being processed multiple times.

Terminal

aws sqs delete-message --queue-url https://sqs.us-east-1.amazonaws.com/123456789012/my-queue --receipt-handle AQEBwJnKyrHigUMZj6rYigCgxlaS3SLy0a...

Expected Output

No output (command runs silently)

→

--queue-url - Specifies the queue to delete the message from

→

--receipt-handle - Identifies the specific message to delete

Key Concept

If you remember nothing else from this pattern, remember: messaging services let different parts of your system talk safely and reliably without needing to be online at the same time.

Common Mistakes

Not deleting messages after processing them

Messages stay in the queue and get processed again, causing duplicate work or errors

Always delete messages from the queue after you finish processing them

Sending messages to the wrong queue URL

Messages go to a queue that no one reads, so they get lost or delayed

Double-check the queue URL before sending messages

Assuming messages arrive instantly

There can be small delays; your system should handle waiting or retries gracefully

Design your system to poll or wait for messages instead of expecting immediate delivery

Summary

Create a queue to hold messages safely between services.

Send messages to the queue to communicate between parts of your system.

Receive and delete messages to process tasks reliably without losing or repeating work.