Event Hubs Auto-Inflate

Your Azure Event Hubs namespace is provisioned with a fixed number of throughput units. Each one allows a set amount of incoming data per second, say 1 megabyte or 1,000 events, whichever comes first. Azure Event Hubs enforces that limit and doesn't accept more.

Now a sudden spike sends events in far faster than those provisioned units allow. Azure Event Hubs starts rejecting the extra events outright, instead of accepting them, and whatever depended on those events never gets them at all. Not even a little late.

Traffic beyond the provisioned throughput units gets rejected outright, not queued or slowed down. That's exactly what Auto-Inflate fixes.

Auto-Inflate lets that limit grow on its own: turn it on for the Azure Event Hubs namespace, and set a maximum throughput unit limit it's allowed to scale up to. Once that's set, when incoming traffic approaches the current limit, Azure Event Hubs automatically adds more throughput units on its own, up to that maximum, instead of rejecting the extra events.

Use: Azure Event Hubs Auto-Inflate (IsAutoInflateEnabled)

Let the namespace add capacity on its own as traffic climbs, instead of rejecting whatever doesn't fit in what was provisioned ahead of time.

A water main normally carries enough water for a neighborhood's everyday use. During a sudden surge, like a whole street running sprinklers at once, a fixed pipe would just back up and overflow.

A system that widens the pipe on its own during that surge, up to a set maximum width, keeps the water flowing at the higher rate instead of backing up, and narrows back down once the surge passes.

Capacity grows on its own as demand climbs, up to a limit set ahead of time.