A software firm finds that external clients are making repeated calls to an API. The architect plans to defend resources by using rate-limiting. Which approach would address this while balancing user experience with system protection?
Enforce usage thresholds based on the origin of each request
Use a load balancer for widespread traffic distribution
Rate-limiting enforces constraints on calls to an API (Application Programming Interface) over a defined interval to help prevent resource overuse and maintain reliable performance. Adjusting thresholds per originating client helps manage bursts of calls effectively. Using a load balancer spreads general traffic flow but does not limit frequent connections from an identical source. Dividing networks with micro-segmentation enhances isolation without regulating persistent calls. A DNS aggregator provides domain lookups but does not handle recurring requests from a single entity.
Ask Bash
Bash is our AI bot, trained to help you pass your exam. AI Generated Content may display inaccurate information, always double-check anything important.
What is rate-limiting in the context of APIs?
Open an interactive chat with Bash
How does rate-limiting based on origin differ from other strategies?
Open an interactive chat with Bash
Why doesn’t a load balancer replace the need for rate-limiting?