AspNetCoreRateLimit
SoapCore
Our great sponsors
| AspNetCoreRateLimit | SoapCore | |
|---|---|---|
| 5 | 4 | |
| 3,048 | 957 | |
| - | 1.8% | |
| 1.0 | 8.8 | |
| about 1 month ago | 20 days ago | |
| C# | C# | |
| MIT License | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
AspNetCoreRateLimit
-
.Net 7 rate limiting with redis distributed cache with tenant based architecture
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
-
ASP.NET Core rate limiting middleware in .NET 7
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.
- Can I protect an controller endpoint from getting brute forced?
-
How to implement API Rate limiting/throttling [.Net Framework 4.5]
Have a look at this package: https://github.com/stefanprodan/AspNetCoreRateLimit
-
Stream Emojis - Build it yourself 🛠
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.
SoapCore
-
Questions about OWIN and WCF from a high level.
If you have a need to still support existing client apps that used a WCF backend then this or SoapCore are both options but I don’t think they have full support for all features that WCF had.
-
20 years of .NET: Reflecting on Microsoft's not-Java
Insted of CoreWCF we used SoapCore which is way more stable https://github.com/DigDes/SoapCore/
-
How do I explain .NET 5/6 to people not keeping up with it?
For WCF: https://github.com/DigDes/SoapCore
-
Contract First Web Service Development in .NET
Sure, we could use Soap Core, but to work with existing contracts I find it to be a very manual solution and with some risk of inadvertently altering the schema.
What are some alternatives?
Ocelot - .NET API Gateway
CoreWCF - Main repository for the Core WCF project
practical-aspnetcore - Practical samples of ASP.NET Core 8.0, 7.0, 6.0, 5.0, 3.1, 2.2, and 2.1,projects you can use. Readme contains explanations on all projects.
Carter - Carter is framework that is a thin layer of extension methods and functionality over ASP.NET Core allowing code to be more explicit and most importantly more enjoyable.
nopCommerce - ASP.NET Core eCommerce software. nopCommerce is a free and open-source shopping cart.
ServiceStack - Thoughtfully architected, obscenely fast, thoroughly enjoyable web services for all
Electron.NET - :electron: Build cross platform desktop apps with ASP.NET Core (Razor Pages, MVC, Blazor).
botbuilder-community-dotnet - Part of the Bot Builder Community Project. Repository for extensions for the Bot Builder .NET SDK, including middleware, dialogs, recognizers and more.
aspnetcore-redis-rate-limiting - Set up a Redis backplane for ASP.NET Core multi-node deployments, using the built-in Rate Limiting support that's part of .NET 7 and .NET 8.
Jackett - API Support for your favorite torrent trackers