Queue Storage overview

Develop Azure Event-based and Message-based Solutions

Fiodar Sazanavets

Senior Software Engineer and Microsoft MVP

Introduction to message queues

Background workers and message queues

Message queues overview

TODO list for the cloud.
Asynchronous and doesn't block users.
Processed lightweight messages.
Background workers process messages.

Message queue

Queue Storage overview

Azure Queue Storage is the simplest way to set up message queues in Azure.
Applications connect to a queue using a connection string.
Messages are processed in the order they are added to the queue.

Azure Queue Storage

Queue triggers

Each message is picked up by a queue trigger.
After successful processing, the message disappears from the queue.
The trigger connects to the queue using a connection string.
The function runs automatically while messages remain in the queue.

Queue trigger

Error handling

Poison queue

If a queue trigger fails while processing a message, an error is returned.
The message is removed from the main queue and placed in a poison queue.
This prevents the failed message from blocking the main queue.
Failed messages can be handled or reviewed later.

Delaying and batching

Message delays

Scheduled to be sent later
Done via initial invisibility delay

Batching

Multiple messages processed in a batch
Improves throughput
Makes the system faster

Message delays

Message batching

Messages vs events

Message-based:
- Intended for a specific consumer.
- Pull-oriented.
Event-based:
- Something happened.
- Push-oriented.
When to use what:
- Queues for reliable background work.
- Events to notify independent services that something happened.

Event-based vs message-based

Let's practice!

Develop Azure Event-based and Message-based Solutions

Preparing Video For Download...