57 packages tagged with “throttling”
WebApiThrottle message handler and action filter are designed for controlling the rate of requests that clients can make to an API based on IP address, client API key and request route. WebApiThrottle works with ASP.NET Web API hosted is IIS, Owin with IIS and Owin self-hosted.
MvcThrottle filter is designed for controlling the rate of requests that clients can make to a website based on IP address, request route, user-agent and client identity. You can set multiple limits for different scenarios like allowing an IP to make a maximum number of calls per second, per minute, per hour or per day. You can define these limits to address all requests made to your website or you can scope the limits to each Controller, Action or URL, with or without query string params.
Popular rate limiting algorithms. C# implementations of fixed token bucket and leaky token bucket throttling strategies
A simple package contains basic crud functions, bad word replacer, rate limiter(throttling) and basic email service using mongodb
Brake Pedal is a general purpose throttling library. The library provides the following features: - Time based throttling: limit X number of requests over Y time period. - Locking: block requests after X attempts over Y time period for Z time period. - Decoupled storage: you can use the bundled repositories (in memory) or roll your own. The BrakePedal.Http package provides code to use the BrakePedal library in a Web API application as an attribute, handler, or filter. The BrakePedal.Redis package contains an implementation of a Redis BrakePedal repository which uses StackExchange.Redis (https://github.com/StackExchange/StackExchange.Redis) for use with the BrakePedal library.
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.
Rate limiting library for .NET/ASP.NET Core
The BrakePedal.Redis package contains an implementation of a Redis BrakePedal repository which uses StackExchange.Redis (https://github.com/StackExchange/StackExchange.Redis) for use with the BrakePedal library.
Super simple API throttling / rate limit framework based on attributes
Package Description
HTTP API client library
Rate limiting library for Azure Functions
CounterStore for ThrottlingTroll. Stores counters in Redis.
CounterStore for ThrottlingTroll. Stores counters in an Azure Table/Cosmos DB with Table API.
CounterStore for ThrottlingTroll. Stores counters in ASP.Net Core's IDistributedCache.
The BrakePedal.Http package provides code to use the BrakePedal library in a Web API application as an attribute, handler, or filter.
Pauses the program execution when an specified rate limit has been exceeded.
Rate limiting library for Azure Functions with ASP.NET Core integration
A .NET library that provides a class that uses SemaphoreSlim but allows a negative initialCount. This could be used, for example, when starting to throttle requests but initially already have more concurrent requests than the maximum you want to start allowing.
This is a project made from MvcThrottle by Stefan Prodan. Stefan Prodan have made a great librairy, but it is now archived. I've change the encryption of the project to be FIPS compliance. For more information see the documentation of Stefan Prodan at : https://github.com/stefanprodan/MvcThrottle#mvcthrottle
WebApiThrottle message handler and action filter are designed for controlling the rate of requests that clients can make to an API based on IP address, client API key and request route. WebApiThrottle works with ASP.NET Web API hosted is IIS, Without Owin.
The library contains multiple controller types implementing different throttling strategies: Linear throttling - limits the number of calls by enforcing specified delay between consequent requests; Short Average - limits the number of calls by specified number of requests per configured duration; it does not limit overall number of requests, but rather assures blocking excessive requests; this strategy is very helpful to cut the requests flooding caused by such user behaviors as multi-click or hard click on F5 button; 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 uniquely determines the client making requests. It does not purely rely on client IP address allowing multiple clients from the same network concurrently making requests to the IIS. 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 whether it logs blocking information to IIS log, but allows request to continue. The log-only mode is very useful when there is a need to determine the most appropriate throttling configuration parameters. The code is highly optimized having very low memory impact and taking less than 0.3 ms to run on a regular development laptop. As an extra functionality it provides with real-time snapshot of current throttling status for all controllers. The snap-shot is available online as a JSON output. It requires configuration to assure authorized used as desired by an application.
ASP.NET Core rate limiting middleware based on Regular Expressions for Urls
Use this to ensure that events aren't handled too frequently.
User throttling for ASP.NET MVC