A million taps a second. One tiny message.
25 million people tapping 🔥 at the same moment — and not one of those taps is ever delivered to anyone.
What you'll learn
- The live-reactions use case in four steps — what the app actually owes every viewer
- Why sending every reaction to every viewer is impossible, in one line of maths
- The five Azure services that count instead — Front Door, Container Apps, Event Hubs, Stream Analytics, Web PubSub
Share this passage
Drawing…
Understand it one step at a time
The short runs these in order in about 70 seconds. Here they are written out — pick any step to jump the short straight to it.
25 million people, one ball
25 million viewers, one final ball of the match. Watch the reactions land — this is a single second of live traffic, not the whole game.
Frequently asked questions
- Why can't you just broadcast every reaction tap to every viewer?
- The maths doesn't scale — a million viewers each tapping becomes a million events, and delivering each one to a million other viewers is a delivery count that grows with the square of the audience. What was supposed to be growth becomes the outage.
- How is a live reactions feature actually built at scale?
- Reactions are counted rather than individually delivered — Front Door, Container Apps, Event Hubs, Stream Analytics and Web PubSub each handle one stage (ingest, aggregate, fan-out), so viewers see an updating count instead of every raw tap.
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.
Read deeper on Azure
Twenty seconds gets the shape of an idea across. These go into how it behaves in production.
-
How Azure Protects a Mobile App: The Full Request Flow, Layer by Layer
Front Door, your API, Microsoft Entra ID, authorization and a private database — the five layers that stand between a mobile app and its data on Azure.
-
Your Mobile App Is Leaking Its API Key — and Obfuscation Will Not Save It
An APK or IPA is a zip file. Anything hardcoded inside it, including your API key, is already public — and here is how to get it off the phone for good.
-
What Is Microsoft Foundry (Azure AI Foundry)? The Services, and When You Actually Need Them
A plain tour of Microsoft Foundry for developers: the resource, projects, models, agents, tools, and when Azure OpenAI on its own is enough.
More shorts
-
Azure
Secure a Mobile API in 5 Steps
8 steps · 25s
-
Azure
What Happens When You Tap Sign In
8 steps · 25s
-
Azure
Your Mobile App Is Leaking Its API Key
8 steps · 26s
Get new posts by email
New technical articles, Azure AI and GitHub Copilot updates, and upcoming events. No spam, unsubscribe anytime.
MSDEVBUILD
/ blog Multi-Stack Dev Build · by Suthahar Azure