Skip to content

PATTERN Cited by 1 source

Ingress rate limiting and quarantine

Definition

Place traffic-control enforcement upstream of the streaming substrate (before events reach Kafka brokers) rather than relying on the broker to absorb every spike. Two complementary controls:

  • Rate limiting: Dynamic per-tenant, per-topic, per-producer, or per-traffic-class limits enforced at the API/delivery layer.
  • Quarantine: Traffic that is malformed or repeatedly failing is diverted to a safe holding path instead of retrying indefinitely through the hot path.

Why it matters

At extreme scale (150B+ events/day), a single misconfigured producer or a burst of malformed events can saturate shared broker capacity, affecting all tenants. Moving the protection boundary closer to producers means Kafka is never asked to be the admission-control system — it remains the durable, ordered log.

Seen in

Last updated · 602 distilled / 1,824 read