Request throttling using pi-es controller

A distributed computing system comprising:

• one or more processors;
• and
• one or more memories storing computer-executable instructions that, when executed with the one or more processors, cause the distributed computing system to:
• receive, at a throttler engine of the distributed computing system, a plurality of requests to use a software component, each request of the plurality of requests associated with a request time;
• aggregate, by the throttler engine, a subset of the plurality of requests based at least in part on a time window, the request times of each of the requests in the subset corresponding to the time window, and the subset aggregated into a queue;
• determine, based at least in part on the subset of the plurality of requests, a received request rate;
• identify a request rate limit associated with the software component, the request rate limit corresponding to the time window;
• compute, based at least in part on the received request rate and the request rate limit, a plurality of correction values;
• determine a throttled request rate based at least in part on the plurality of correction values;
• identify one or more throttled requests from the subset, wherein the one or more throttled requests correspond to the throttled request rate;
• and
• provide the one or more throttled requests to the software component.

A computer readable medium storing computer-executable instructions that, when executed by one or more processors, cause a distributed computing system to at least:

• receive, at a throttler engine of the distributed computing system, a plurality of requests to use a software component, each request of the plurality of requests associated with a request time;
• aggregate, by the throttler engine, a subset of the plurality of requests based at least in part on a time window, the request times of each of the requests in the subset corresponding to the time window, and the subset aggregated into a queue;
• determine, based at least in part on the subset of the plurality of requests, a received request rate;
• identify a request rate limit associated with the software component, the request rate limit corresponding to the time window;
• compute, based at least in part on the received request rate and the request rate limit, a plurality of correction values;
• determine a throttled request rate based at least in part on the plurality of correction values;
• identify one or more throttled requests from the subset, wherein the one or more throttled requests correspond to the throttled request rate;
• and
• provide the one or more throttled requests to the software component.