Built-in Rate Limiting support - part of .NET 7

[cristipufu]

If you haven't heard yet, .NET 7 comes with built-in support for Rate Limiting (in-memory): https://devblogs.microsoft.com/dotnet/announcing-rate-limiting-for-dotnet/

I have created another repository for multi-node deployments (with Redis) and my future contributions will be focused on this new library: https://github.com/cristipufu/aspnetcore-redis-rate-limiting

[andygarratt]

I believe the built in support is overall and not per IP?

[SteveDurkee]

I believe the built in support is overall and not per IP?

This can be accomplished using the PartitionedRateLimiter. Using the built in PartitionedRateLimiter.Create method and defining a partition per IP.

[iXab3r]

It could only be applied on Global level.
For endpoints there is an open issue dotnet/aspnetcore#42691
Seems strange that such a basic scenario (multiple different rules for a single endpoint) is not supported by default.

[vmandic]

Any migration guidelines on how to switch over with Redis support from this nuget to new one?

EDIT: I am using app.UseIpRateLimiting(); and huge appsettings conf: services.Configure<IpRateLimitOptions>(Configuration.GetSection("IpRateLimiting"));

[muhammadganji]

there is any way to implement RateLimit Based on IP v6 in .net7 ?
I can't find out the document of Microsoft, it's complex

[Deali-Axy]

So far (.net8) Microsoft.AspNetCore.RateLimiting is not good, although it is built-in, but not as good as AspNetCoreRateLimit out of the box

[pampua84]

Hi everyone,
I’ve encountered an issue with the new .NET 7/8 rate limiter: it lacks several features from the previous version, including the rate limiter for ClientId. What are your thoughts? Should we attempt to integrate the old features into the new repository, or is it better to continue using the current one, considering they offer distinct approaches to rate limiting?

[Deali-Axy]

I would suggest to keep using the current features, Microsoft is always slow to move officially, still no need to integrate the old features into the new repository, right?

[princegearydymosco]

Hi, I'm upgrading a web API project from .NET 6 to .NET 8. Would you recommend continuing to use AspNetCoreRateLimit? I've tested the package, and there seem to be breaking changes.

[jmbryan4]

So it looks like AspNetCoreRateLimit still has advantages over .NET 8’s built-in rate limiting (e.g., IP & ClientId based rate limiting per endpoint). However, aspnetcore-redis-rate-limiting fully integrates with .NET 8’s rate limiting middleware for request-based distributed rate limiting but lacks some of the features this project offers.

I also noticed several open PRs and issues on this project. Are these going to be addressed or is all future work only on aspnetcore-redis-rate-limiting? @cristipufu