in theory (and also probably in practice) it's a control theory problem and there are already algorithms and ideas out there - here is an article not exactly about rate limiting but implementing something based on this might work really well: https://www.eecs.umich.edu/courses/eecs571/reading/control-t...

Aperture project's policy language is indeed inspired by Control Systems, especially PID Control.

See: https://docs.fluxninja.com/concepts/advanced/circuit

This article was crossposted to hell and back last week on reddit. And it has an AI vibe…

Thanks for the feedback - This blog could have been better and less aggressively distributed. At the same time, we should consider the credible body of work behind this. It's not AI-generated spam but backed by actual code that provides a reference implementation behind the idea.

See: https://github.com/fluxninja/aperture

It’s a blog post, it will be judged by its content. It does feel like at a minimum it was heavily edited with an AI assistant, verbose and elegant but light on specifics. And if the goal is to get people hooked on how to implement adaptive rate limiting (and maybe adopt fluxninja) it doesn’t seem to be hitting the right note.

Thanks for the feedback :). I will try to be more specific in next blog.

It's a blog on an open-source project that precisely tells you how to implement adaptive rate limiting.

Just click around a bit:

- https://github.com/fluxninja/aperture

- https://docs.fluxninja.com/use-cases/adaptive-service-protec...

Note: I am one of the authors' of this project.

Thanks for the feedback. I agree I could've gone into more technical depth and implementation details. So, taking your feedback in account, I've modified and added more details in the blog. But, I already have a next blog in planning covering the topic in-depth, along the similar lines of your feedback, because of that I didn't intend to make a long one, decided to split the blog :)