Somebody said “we need Kafka”.
A broker and a log are not two brands of the same thing.
What you'll learn
- The real difference between a broker and an append-only log
- Why Kafka partitions put a ceiling on your consumer count
- When the Event Hubs Kafka endpoint is the cheaper answer
Share this passage
Drawing…
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.
Somebody said “we need Kafka”
It gets said in design reviews constantly, usually as a reflex — an answer to a question about scale nobody actually asked out loud.
Frequently asked questions
- What's the fundamental difference between Service Bus and Kafka?
- Service Bus is a message broker — messages are consumed and removed. Kafka is an append-only log — messages persist and can be replayed by any number of consumers reading at their own offset. They solve different problems even though both move data between services.
- Should you pick Kafka just because a queue seems too simple?
- No — taking on Kafka is really a decision to take on its operational overhead (partitions, cluster management, rebalancing), and that's only worth it for its ecosystem or replay guarantees. Azure Event Hubs' Kafka-compatible endpoint is often the cheaper way to get Kafka's protocol without running a cluster.
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.
-
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.
More shorts
-
Azure
Money debited. Order failed.
10 steps · 56s
-
Azure
One tap. Two orders.
10 steps · 57s
-
Azure
1.6 million downloads. One photo.
10 steps · 58s
Get new posts by email
New technical articles, Azure AI and GitHub Copilot updates, and upcoming events. No spam, unsubscribe anytime.