Suthahar Jegatheesan MSDEVBUILD / blog Multi-Stack Dev Build · by Suthahar
Search
Azure

Three teams. One queue. Everyone missed messages.

A queue is a DM. A topic is the group broadcast. The difference is a real bug.

What you'll learn

  • Why three teams on one queue each get a third of the messages
  • How competing consumers differ from real subscribers
  • What a subscription gives you that a second reader never will
Azure 10 steps 32 seconds —views

Was this useful?

Share

Understand it one step at a time

The short runs these in order in about 32 seconds. Here they are written out — pick any step to jump the short straight to it.

1 Step 1 of 10

One message. Who gets it?

Billing, analytics and audit all need to know the same order was placed. One event, and all three teams are listening for it.

Frequently asked questions

Why did three teams reading one Service Bus queue each only get a third of the messages?
A queue's readers are competing consumers — each message goes to exactly one of them, so adding more readers to the same queue divides the work rather than giving everyone a copy.
What actually gives every team its own copy of a message?
A subscription on a topic, not a second reader on a queue. Each subscription gets its own copy of every message that matches its filter, which is duplication rather than division.

Free app · no app store

These are built for a phone

Every short is drawn at full portrait height, the shape a phone already is. Installed, it opens full-bleed with no address bar across the top — and the whole library reads offline.

How it works

Read deeper on Azure

Twenty seconds gets the shape of an idea across. These go into how it behaves in production.

More shorts

Get new posts by email

New technical articles, Azure AI and GitHub Copilot updates, and upcoming events. No spam, unsubscribe anytime.

↑↓ navigate ↵ open