Service Bus queues concept in Azure - Step-by-Step Execution

Process Flow - Service Bus queues concept

Sender sends message

↓

Message enters queue

↓

Message waits in queue

↓

Receiver reads message

↓

Receiver processes message

↓

Receiver deletes message from queue

↓

Queue ready for next message

This flow shows how a message moves from sender to receiver through the Service Bus queue, waiting until processed and deleted.

Execution Sample

Azure

Send message 'Hello'
Message stored in queue
Receiver reads message
Receiver processes message
Receiver deletes message

This sequence shows a message sent to the queue, then received and removed after processing.

Process Table

Step	Action	Queue State	Message State	Result
1	Sender sends 'Hello'	Empty	Message created	Message added to queue
2	Message stored in queue	Contains 'Hello'	Waiting	Message ready for receiver
3	Receiver reads message	Contains 'Hello'	Locked for processing	Receiver has message
4	Receiver processes message	Contains 'Hello'	Processing	Message being handled
5	Receiver deletes message	Empty	Deleted	Message removed from queue

💡 Message deleted, queue empty, ready for next message

Status Tracker

Variable	Start	After Step 1	After Step 2	After Step 3	After Step 4	Final
Queue	Empty	Contains 'Hello'	Contains 'Hello'	Contains 'Hello'	Contains 'Hello'	Empty
Message State	None	Created	Waiting	Locked for processing	Processing	Deleted

Key Moments - 3 Insights

Why does the message stay in the queue after the receiver reads it?

Because the message is locked for processing but not deleted yet, as shown in step 3 and 4 of the execution_table.

What happens if the receiver crashes before deleting the message?

The message lock expires and the message becomes available again in the queue for another receiver, ensuring no message loss.

Can multiple receivers get the same message at the same time?

No, the message is locked to one receiver at a time to avoid duplicate processing, as seen in the 'Locked for processing' state.

Visual Quiz - 3 Questions

Look at the execution_table, what is the queue state after the receiver reads the message?

A Contains 'Hello'

B Empty

C Deleted

D Locked

💡 Hint

Check step 3 in the execution_table under 'Queue State'

At which step does the message get removed from the queue?

A Step 3

B Step 4

C Step 5

D Step 2

💡 Hint

Look at the 'Result' column in the execution_table for when the message is deleted

If the receiver never deletes the message, what happens to the message state?

A It becomes 'Deleted'

B It remains 'Locked' until lock expires

C It stays 'Waiting' forever

D It is immediately removed

💡 Hint

Refer to key_moments about message lock and processing

Concept Snapshot

Service Bus queues hold messages sent by senders.
Messages wait in the queue until a receiver reads them.
Reading locks the message for processing.
Receiver deletes message after processing.
If not deleted, message lock expires and message returns to queue.
This ensures reliable, one-at-a-time message processing.

Full Transcript

Service Bus queues work like a mailbox for messages. A sender puts a message into the queue. The message waits there until a receiver reads it. When the receiver reads the message, it locks it so no one else can process it at the same time. The receiver then processes the message and deletes it from the queue. If the receiver crashes or does not delete the message, the lock expires and the message becomes available again. This way, messages are processed reliably and only once.