Message ordering and sessions in Azure - Mini Project: Build & Apply

Azure Service Bus: Message Ordering and Sessions

📖 Scenario: You are building a messaging system for a retail application. Orders must be processed in the exact order they are received per customer. To achieve this, you will use Azure Service Bus with sessions to ensure message ordering for each customer's order stream.

🎯 Goal: Create an Azure Service Bus queue with sessions enabled to guarantee message ordering per customer session.

📋 What You'll Learn

Create an Azure Service Bus queue named orders

Enable sessions on the orders queue

Set the MaxDeliveryCount to 10

Set the LockDuration to 1 minute

Configure DefaultMessageTimeToLive to 14 days

💡 Why This Matters

🌍 Real World

Message ordering per customer is critical in retail order processing to avoid confusion and ensure correct fulfillment.

💼 Career

Understanding how to configure Azure Service Bus queues with sessions is essential for cloud architects and developers building reliable, ordered messaging systems.

1

Create the basic Azure Service Bus queue

Write the Azure Resource Manager (ARM) template snippet to create a Service Bus queue named orders inside a resource group. Include only the basic queue resource with the name property set to orders.

Azure

# Your code here to create a Service Bus queue named 'orders'

Hint

Use the resource type Microsoft.ServiceBus/namespaces/queues and set the name property to orders.

2

Enable sessions on the queue

Add the property requiresSession and set it to true inside the properties of the orders queue to enable message sessions.

Azure

{
  "type": "Microsoft.ServiceBus/namespaces/queues",
  "apiVersion": "2021-06-01-preview",
  "name": "orders",
  "properties": {
    // Add requiresSession property here
  }
}

Hint

Inside properties, add "requiresSession": true to enable sessions.

3

Configure delivery count, lock duration, and message TTL

Inside the properties of the orders queue, add these exact properties: maxDeliveryCount set to 10, lockDuration set to "PT1M" (1 minute), and defaultMessageTimeToLive set to "P14D" (14 days).

Azure

{
  "type": "Microsoft.ServiceBus/namespaces/queues",
  "apiVersion": "2021-06-01-preview",
  "name": "orders",
  "properties": {
    "requiresSession": true
    // Add maxDeliveryCount, lockDuration, and defaultMessageTimeToLive here
  }
}

Hint

Use ISO 8601 duration format for lockDuration and defaultMessageTimeToLive.

4

Complete the ARM template with namespace and queue resource

Wrap the orders queue resource inside a Service Bus namespace resource named retailnamespace. Use Microsoft.ServiceBus/namespaces as the type for the namespace. The queue resource should be a child resource of the namespace. Use API version 2021-06-01-preview for both resources.

Azure

{
  // Add namespace resource wrapping the queue resource here
  // Namespace name: retailnamespace
  // Queue name: orders
}

Hint

Use nested resources array inside the namespace resource to define the queue.

Practice

1. What is the main purpose of using sessions in Azure Service Bus messaging?

easy

A. To group related messages and keep their order

B. To encrypt messages for security

C. To increase message size limits

D. To automatically retry failed messages

Solution

1. Step 1: Understand session concept in messaging

   Sessions are used to group related messages so they can be processed in order.

2. Step 2: Identify the purpose of sessions

   Sessions ensure messages with the same session ID are received and processed sequentially.

3. Final Answer:

   To group related messages and keep their order -> Option A

4. Quick Check:

   Sessions = Group messages + order [OK]

Hint: Sessions keep related messages ordered by session ID [OK]

Common Mistakes:

• Thinking sessions encrypt messages
• Assuming sessions increase message size
• Confusing sessions with retry policies

2. Which property must be set on a message to assign it to a session in Azure Service Bus?

easy

A. message_id

B. correlation_id

C. session_id

D. partition_key

Solution

1. Step 1: Identify session assignment property

   The property used to assign messages to sessions is session_id.

2. Step 2: Differentiate from other properties

   message_id identifies messages uniquely, correlation_id links related messages but not for sessions, partition_key is for partitioning.

3. Final Answer:

   session_id -> Option C

4. Quick Check:

   Assign session = session_id property [OK]

Hint: Use session_id to assign messages to sessions [OK]

Common Mistakes:

• Using message_id instead of session_id
• Confusing correlation_id with session_id
• Using partition_key for session assignment

3. Given the following code snippet receiving messages by session, what will be the order of processing?

var receiver = client.AcceptSessionAsync("order123");
var message1 = await receiver.ReceiveMessageAsync();
var message2 = await receiver.ReceiveMessageAsync();

Assuming messages with session_id "order123" were sent in order: M1, M2.

medium

A. M1 processed before M2

B. M1 and M2 processed in any random order

C. Only M2 will be processed

D. M2 processed before M1

Solution

1. Step 1: Understand session receiver behavior

   Accepting a session locks it and receives messages in the order they were sent for that session.

2. Step 2: Analyze message receiving calls

   The first call receives the first message (M1), the second call receives the next message (M2), preserving order.

3. Final Answer:

   M1 processed before M2 -> Option A

4. Quick Check:

   Session receiver = ordered messages [OK]

Hint: Session receiver processes messages in sent order [OK]

Common Mistakes:

• Assuming messages arrive out of order
• Thinking only last message is received
• Confusing session with non-session receivers

4. You have a session-enabled queue but your receiver code throws an error when calling AcceptSessionAsync(). What is the most likely cause?

medium

A. The session_id property is missing on messages

B. The message size exceeds the limit

C. The client connection string is invalid

D. The queue is not session-enabled

Solution

1. Step 1: Check queue session configuration

   AcceptSessionAsync requires the queue to be session-enabled; otherwise, it throws an error.

2. Step 2: Differentiate from other causes

   Missing session_id causes messages to be non-sessioned but does not cause AcceptSessionAsync to fail; invalid connection or message size cause different errors.

3. Final Answer:

   The queue is not session-enabled -> Option D

4. Quick Check:

   AcceptSessionAsync error = queue not session-enabled [OK]

Hint: AcceptSessionAsync needs session-enabled queue [OK]

Common Mistakes:

• Assuming missing session_id causes AcceptSessionAsync error
• Blaming connection string without checking queue settings
• Confusing message size errors with session errors

5. You need to process orders in the exact order they were placed, but orders come from multiple customers simultaneously. How should you design your Azure Service Bus solution to ensure correct ordering per customer?

hard

A. Use multiple queues, one per customer, without sessions

B. Use a single session-enabled queue and assign each customer's messages a unique session_id

C. Use a single queue without sessions and process messages as they arrive

D. Use topics and subscriptions without sessions

Solution

1. Step 1: Understand ordering per customer requirement

   Ordering must be maintained per customer, but customers send messages concurrently.

2. Step 2: Choose session-enabled queue with unique session_id per customer

   Assigning each customer's messages a unique session_id groups their messages, preserving order within that session.

3. Step 3: Evaluate other options

   Single queue without sessions loses order; multiple queues add complexity; topics/subscriptions don't guarantee order per customer.

4. Final Answer:

   Use a single session-enabled queue and assign each customer's messages a unique session_id -> Option B

5. Quick Check:

   Session-enabled queue + unique session_id = per-customer order [OK]

Hint: Use session_id per customer in session-enabled queue [OK]

Common Mistakes:

• Ignoring sessions and losing order
• Using multiple queues unnecessarily
• Relying on topics without ordering guarantees