AspNetCoreRateLimit
Ocelot
Our great sponsors
AspNetCoreRateLimit | Ocelot | |
---|---|---|
5 | 7 | |
3,028 | 8,108 | |
- | 0.9% | |
2.9 | 8.5 | |
2 months ago | 2 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.
Ocelot
-
Some useful Libraries for .NET projects
Ocelot Github Nuget: Install-Package Ocelot -Version 17.0.0
-
An Introduction to Microservices pt. 2
Ok, now that you created you Web API, it's time to work on your API Gateway. Start by adding the Ocelot package to your Gateway project:
-
Opensource API GW that allows transformation and logic/policy creation?
I'd look for an open-source gateway using the programming language that you're familiar with. I was working multiple times with the custom API GW (including building my own for fun), and if you're familiar e.g. with C# take a look at this one https://github.com/ThreeMammals/Ocelot or even better https://github.com/microsoft/reverse-proxy If you need to build something really custom, there's a small chance that you will find a plug & play solution.
-
Atlassian Cloud ToS section 3.3(I) prohibits discussing performance issues
Lol, i guess your answer explains a lot about relevant knowledge into web architecture
Eg. Ocelot - https://github.com/ThreeMammals/Ocelot
What are some alternatives?
RestSharp - Simple REST and HTTP API Client for .NET
Refit - The automatic type-safe REST library for .NET Core, Xamarin and .NET. Heavily inspired by Square's Retrofit library, Refit turns your REST API into a live interface.
SoapCore - SOAP extension for ASP.NET Core
Simple.OData.Client
RestEase - Easy-to-use typesafe REST API client library for .NET Standard 1.1 and .NET Framework 4.5 and higher, which is simple and customisable. Inspired by Refit
Flurl.Http - Fluent URL builder and testable HTTP client for .NET
Zuul - Zuul is a gateway service that provides dynamic routing, monitoring, resiliency, security, and more.
FastEndpoints - A light-weight REST API development framework for ASP.Net 6 and newer. [Moved to: https://github.com/FastEndpoints/Library]
unit-test - Estudos sobre Testes unitários
WebApiClient - An open source project based on the HttpClient. You only need to define the c# interface and modify the related features to invoke the client library of the remote http interface asynchronously.
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.