[EPIC] Rate limiting

[BrennanConroy]

• Resource limit API design Resource limit API review aspnetcore#32030
• Redis based Resource Limiter shipped in aspnetcore
• Limits in Kestrel Use resource limits in Kestrel aspnetcore#32033
  • Existing rate limits
  • Concurrency and rate limits for connections
• Limiter Middleware Rate and Concurrency limiting middleware aspnetcore#32032
• Uses in BCL types Usage of resource limit APIs in BCL aspnetcore#32039
  • Pipelines
  • Channels
  • Streams
  • HttpClient
• Adoption in YARP Adopt resource limit APIs in YARP aspnetcore#32040
• Adoption for ATS, ACR, R9, etc Ensure resource limit APIs can be used by existing implementations aspnetcore#32041

[ghost]

Thanks for contacting us.
We're moving this issue to the Next sprint planning milestone for future evaluation / consideration. We will evaluate the request when we are planning the work for the next milestone. To learn more about what to expect next and how this issue will be handled you can read more about our triage process here.

[khellang]

Here's to hoping you'll need these APIs to track rate limiting dotnet/runtime#36386 🙏🏻

[davidfowl]

We won't use IDistributedCache 😄

[khellang]

Where are you storing used capacity? Just bypassing the existing abstractions entirely?

[davidfowl]

There would be an abstraction specifically for rate limiting.

[khellang]

OK, that's fine, but at some point you have to store something. Will that not be in a... let's say... distributed cache? 😅

[jkotalik]

@JunTaoLuo should this issue be assigned to you?

[JunTaoLuo]

Sure this touches on dotnet/aspnetcore#29933

[davidfowl]

I think we should break this issue up.

[mairaw]

Bulk closing .NET 6 epics and user stories. If you think this issue was closed in error, please reopen the issue and update it accordingly.