Found 162 packages
Angular.Throttle binding library for Bridge.NET projects.
Lodash.Throttle binding library for Bridge.NET projects.
A collection of useful data and execution extensions for .NET
Es.Throttle
适用于.Net Core WebApi接口限流框架
Package Description
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.
Throttle binding library for Bridge.NET projects.
Throttle Debounce (throttle-debounce) binding library for Bridge.NET projects.
P Throttle (p-throttle) binding library for Bridge.NET projects.
Service discovery kit for .NET microservices - Throttle
.NET library designed to facilitate debounce and throttle mechanisms in distributed system environments, leveraging Redis for state management and distributed locking. This ensures that function executions are properly debounced or throttled across multiple instances, preventing excessive or unintended operations.
Package Description
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.
A small .NET Core library providing a simple thread-safe object which throttles an arbitrary set of actions, rate limiting them to the specified number of actions within the specified timespan.
JoyMoe.Common Attributes for Asp.Net Core MVC
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.
Package Description
Package Description