liveBook · Manning

Network throttling

Network throttling is the deliberate limitation or simulation of network or request-processing rates to control resource use or evaluate behavior under constrained conditions.

How 2 Manning books explain it

Kafka Streams in Action, Second Edition

Throttling is the deliberate limitation of request or operation frequency by delaying execution between attempts.

How it is used
Limits external API calls inside Kafka Connect source-task polling.
How deep it goes
Explains interval calculation, sleeping, empty-result handling, and worker responsiveness without broader rate-limit strategies.
Examples
Uses a StockTickerSourceTask that polls a stock-service API and returns SourceRecord data.
What you can do after
Operate a throttled SourceTask that spaces API calls and remains interruptible when no records exist.

Read how Kafka Streams in Action, Second Edition explains network throttling →

Apache Kafka in Action

Throttling is the deliberate delaying or muting of client requests to keep resource usage within an enforced limit.

How it is used
Protects Kafka clusters from overloaded producers, consumers, and uneven resource consumption.
How deep it goes
Explains quota types, scopes, configuration strategy, and per-broker limitations, but does not provide monitoring procedures.
Examples
Uses kafka-configs.sh commands for default, client-specific, and user-specific producer or consumer quotas.
What you can do after
Operate/configure Kafka quotas with kafka-configs.sh and distinguish overload protection from guaranteed capacity.

Read how Apache Kafka in Action explains network throttling →

Related concepts

These guides are generated from the text of Manning books by Manning's knowledge graph and link to the sections they draw on. The full books are available on liveBook and at manning.com.