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

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.

Read deeper on Azure

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

• AI Bot Attacks on a Mobile App Login, and How Azure Stops Them

  A script tries 8,000 passwords a minute against your login API at 3am. Rate limiting, smart lockout and Defender for Cloud make speed the losing move.

• Azure Key Vault Explained: The One Secret Tutorials Never Remove

  Moving every secret into Key Vault leaves exactly one behind: the credential that opens the vault. A managed identity is what removes it.

• How to Secure a Mobile API on Azure in Five Steps, in the Right Order

  HTTPS only, authentication, authorization, secrets and monitoring: five steps to secure a mobile API on Azure, and why the order carries most of the value.