practical-aspnetcore VS AspNetCoreRateLimit

Peruse samples here https://github.com/dodyg/practical-aspnetcore

Check out this repo - https://github.com/dodyg/practical-aspnetcore/tree/net6.0/projects/security/authentication-with-identity

For example, @nitaro (idk the username) shared this GitHub project in one of the past posts that I thought would be a great place to start: https://github.com/dodyg/practical-aspnetcore/tree/net6.0/exercises/pathway-1. I usually work on projects on my own but it’s so much more helpful just having others who are doing the same thing at the same time to bounce ideas off of and get support from!

Check also the samples at https://github.com/dodyg/practical-aspnetcore. It's all tiny samples that you can try out to see some functionalities.

and I maintain a pretty popular open source project https://github.com/dodyg/practical-aspnetcore

AFAIK the new built-in rate limiting only supports in-memory counters at the moment. You will need to use the old open source rate limiting package instead: https://github.com/stefanprodan/AspNetCoreRateLimit

In this post, I wanted to give you some insights about how you can use the ASP.NET Core rate limiting middleware. It’s not as complete as Stefan Prodan’s AspNetCoreRateLimit, but there are enough options available to add rate limiting to your application.

Have a look at this package: https://github.com/stefanprodan/AspNetCoreRateLimit

Eventually I got around to implementing rate limiting on the endpoints, for the dotnet Core WebApi it is really easy to add thanks to the AspNetCoreRateLimit NuGet package. I chose to limit the endpoint to 2 requests per second, per IP Address as well as a limit of 10 requests per 30 seconds per IP Address. Then on the front end I added some messages to let the user know that they are being rate limited and we also limit their ability to spam the same emoji multiple times.