ThrottlingSuite.Http 1.3.1.15

The Throttling Suite provides throttling control capabilities to the .NET Web API applications. It is highly customizable product, yet simple to use. The implementation supports all available hosting options provisioning equal functionality for IIS-hosted and OWIN self-hosted solutions. It is specifically designed to throttle high performance and high throughput Web API applications.

The library contains multiple controller types implementing different throttling algorithms:
Linear throttling - limits the number of calls by enforcing consistent delay between consequent requests;
Short Average - limits the number of calls by specified number of requests per configured duration; it does not intend to limit the overall number of requests, but rather assures blocking excessive requests; this strategy is very helpful to cut the requests floods;
Long Average - limits the number of calls by specified number of requests per configured duration; this strategy limits an overall number of calls within long time duration; this is also known as applying penalty to the client for excessive application use.

Each throttling controller is capable of unique client determination and management. The throttling for any end-point, or set of end-points can be configured either for the entire application, or per-client. It does not purely rely on client IP address, allowing multiple clients from the same network concurrently making requests to the server.
The Throttling Suite allows setting multiple controllers within the application and applying each to a pre-filtered traffic. The filters are also configurable.

The Throttling Suite provides two modes: real blocking mode when request is blocked with 429 HTTP Status code and log-only mode.

The code is highly optimized having very low memory impact. The throttling evaluation functionality takes less than 0.3 ms to run.

The v1.2 is updated to include "Retry-After" response header in the blocked response helping API client to negotiate the request rate with API server side.

The v1.2 also allows to ignore the actual request URL substituting one with Throttling controller instance scope. This provides the benefit to count requests for multiple API endpoints toward the same throttling threshold.

The v1.3 enables configuration from the code rather than XML *.config file.