#ThrottlingTroll is now instrumented with #OpenTelemetry : https://github.com/ThrottlingTroll/ThrottlingTroll/wiki#telemetry

Moved #ThrottlingTroll 's samples into separate repos. https://github.com/ThrottlingTroll/ThrottlingTroll-AspDotNetCore-Samples for ASP.NET Core and https://github.com/ThrottlingTroll/ThrottlingTroll-AzureFunctions-Samples for Azure Functions.

Blogged on how to deduplicate HTTP requests with #ThrottlingTroll: https://scale-tone.github.io/2024/06/02/throttlingtroll-request-deduplication

#ThrottlingTroll (rate-limiting/throttling middleware for ASP.NET Core and Azure Functions) v7.0: https://github.com/ThrottlingTroll/ThrottlingTroll/releases/tag/v7.0 .
.
Now with declarative (attribute-based) configuration. Apply [ThrottlingTrollAttribute] to your controllers/methods/pages/functions to have rate limits defined in-code. And you can now combine all four ways of configuring (declarative, config-file-based, programmatic and reactive) in a single solution. Docs are here: https://github.com/ThrottlingTroll/ThrottlingTroll/wiki .

Finished documentation for #ThrottlingTroll: https://github.com/ThrottlingTroll/ThrottlingTroll/wiki

Someone big has tweeted about #ThrottlingTroll (https://github.com/scale-tone/ThrottlingTroll), so it is now experiencing a reddit effect. Anyway, whoever it was - thank you.

#ThrottlingTroll v3.0. https://github.com/scale-tone/ThrottlingTroll/releases/tag/v3.0 .
Now with the new SemaphoreRateLimitMethod, which limits the number of _concurrent_ requests being processed. In combination with RedisCounterStore, custom IdentityIdExtractor and MaxDelayInSeconds setting this allows to organize named distributed critical sections. Works both with #aspnet and #AzureFunctions.