Azure

15,000 GPS pings a second. Do not put that in a queue.

Partitions, offsets and the reason four teams can read the same event.

What you'll learn

  • Why a queue cannot hand the same event to four teams
  • How a partition key keeps one driver’s pings in order
  • How consumer groups and offsets let a slow reader catch up
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

60,000 drivers. Every 4 seconds

Every car reports GPS position every 4 seconds. Nobody asked for a reply, and no record needs a lock to write it.

Frequently asked questions

Why doesn't a queue work for 60,000 drivers sending GPS pings?
A queue hands each message to exactly one consumer and removes it — if four different teams (routing, billing, safety, analytics) all need the same ping, a queue can't give it to all of them. A partitioned event stream can, because reading doesn't remove the event.
How does Event Hubs keep one driver's pings in order?
By partition key — pings from the same driver land in the same partition, and a partition preserves the order of what was written to it, so one consumer reading that partition sees that driver's pings in order.

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