Global rate limiting for all, multiple routes instead of every route

[neetra]

Expected Behavior / New Feature

Add rate limit options for all requests in common

{
  "Routes": [],
  "RateLimitOptions": [
    {
      "RouteKeys": [ "posts", "users" ],
      "ClientWhitelist": [],
      "EnableRateLimiting": true,
      "Period": "10s",
      "PeriodTimespan": 3,
      "Limit": 1     
    }
  ]
}

Actual Behavior / Motivation for New Feature

We add rate-limiting options for every route :
For e.g:

{
  "DownstreamPathTemplate": "/users",
  "DownstreamScheme": "https",
  "DownstreamHostAndPorts": [
    {
      "Host": "jsonplaceholder.typicode.com",
      "Port": 443
    }
  ],
  "UpstreamPathTemplate": "/users",
  "UpstreamHttpMethod": [ "Get" ],
  "RateLimitOptions": {
    "ClientWhitelist": [],
    "EnableRateLimiting": true,
    "Period": "10s",
    "PeriodTimespan": 3,
    "Limit": 1
  }
}

[ZainHaiderArif]

Any progress on this issue please let me know i am kind of waiting to apply ratelimiting time globally.

[raman-m]

@ZainHaiderArif
It is better to contribute, but not to wait ☝️

Our team (me, @RaynaldM, @ggnaegi) capacity is low and we work on more important issues (performance, a brand new features). But I hope we will work on this feature soon.

And for now, global Rate Limiting feature is available for Dynamic Routing 👉

• Answer 1
• Answer 2

[raman-m]

Related issues

• Apply rate limiting globally  #1915
• Support Global configuration of load balancer and rate limiting options etc for ReRoutes #585

[raman-m]

@neetra Hi Netra!
Are you with Ocelot nowadays?

[raman-m]

Dear @neetra,
Did you read this 👉

• Global Configuration
• Dynamic Routing ❓

[raman-m]

Reopening is due to significant interest from the community...

[orkunseyman]

Hi.
is issue still open to contribute?
Is the expected feature to make the rate limit definitions in the global configuration by grouping the routes?

[raman-m]

@orkunseyman Hello, Orkun!

is issue still open to contribute?

Yes, it is! Currently, there are no open pull requests linked to this issue.
We only have PR #2188, which is related to the Rate Limiting feature.

Is the expected feature to make the rate limit definitions in the global configuration by grouping the routes?

It depends on contribution and its design... However, the requirements of this issue do request some global options to be reused in every route. I believe the easiest solution is to assign global options to all routes exclusively, but implementing some form of grouping should not be difficult.

Are you planning to contribute? When?