Event Grid vs Service Bus decision in Azure - Performance Comparison

Time Complexity: Event Grid vs Service Bus decision

O(n)

Understanding Time Complexity

When choosing between Event Grid and Service Bus, it's important to understand how the number of messages affects processing time.

We want to know how the system's work grows as more events or messages are sent.

Scenario Under Consideration

Analyze the time complexity of sending and receiving messages using Event Grid and Service Bus.

// Event Grid: publish events
for (int i = 0; i < n; i++) {
  await eventGridClient.PublishEventsAsync(new[] { events[i] });
}

// Service Bus: send messages
for (int i = 0; i < n; i++) {
  await serviceBusSender.SendMessageAsync(messages[i]);
}

This code sends n events or messages one by one to each service.

Identify Repeating Operations

Identify the API calls, resource provisioning, data transfers that repeat.

• Primary operation: Sending one event or message per API call.
• How many times: Exactly n times, once for each event or message.

How Execution Grows With Input

As the number of events or messages increases, the total number of send operations increases linearly.

Input Size (n)	Approx. Api Calls/Operations
10	10 send calls
100	100 send calls
1000	1000 send calls

Pattern observation: Doubling the number of events doubles the number of send operations.

Final Time Complexity

Time Complexity: O(n)

This means the time to send all events or messages grows directly in proportion to how many you send.

Common Mistake

[X] Wrong: "Sending many messages at once takes the same time as sending one message."

[OK] Correct: Each message requires its own send operation, so more messages mean more work and more time.

Interview Connect

Understanding how message volume affects processing time helps you design systems that scale well and choose the right messaging service.

Self-Check

What if we batch multiple messages into one send call? How would the time complexity change?