Azure

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
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

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.

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