caddy-ratelimit

At that point you should be rate limiting at the reverse proxy or load balancer. - Nginx https://blog.nginx.org/blog/rate-limiting-nginx - Caddy https://github.com/mholt/caddy-ratelimit - Treafik https://doc.traefik.io/traefik/middlewares/http/ratelimit/ IMO Lambda is kind of an unfair example because the author doesn't mention having multiple instances. Plus a hot take I have is you should not be building an entire web-app as a Lambda or series of Lambda functions... AWS does not have solutions for load balancing in things like APIG so you would have to architect that via DynamoDB or ElastiCache which is the "extra layer or two of overhead" the author mentioned.

While that is true, at that point you should be rate limiting at the reverse proxy or load balancer. - Nginx https://blog.nginx.org/blog/rate-limiting-nginx - Caddy https://github.com/mholt/caddy-ratelimit - Treafik https://doc.traefik.io/traefik/middlewares/http/ratelimit/

It's not like you have to maintain a fork, it's pretty minimal, all you need is a Dockerfile with what you want and build the container. Other than that you just keep bumping the version like you would the standard distribution. For example to use rate limiting I just have a Dockerfile like this: FROM caddy:2.9.1-builder AS builder RUN xcaddy build --with github.com/mholt/caddy-ratelimit FROM caddy:2.9.1 COPY --from=builder /usr/bin/caddy /usr/bin/caddy

You can rate limit HTTP requests (agnostic of specific HTTP versions): https://github.com/mholt/caddy-ratelimit

If you can't already do it with the rate limit module I wrote, open an issue with your detailed requirements: https://github.com/mholt/caddy-ratelimit -- should be pretty straightforward for the most part. > QoS for a shared-multitenant system, in the presence of customers with really badly tuned and spiky request workloads, whose traffic you must nevertheless mostly accept. Yah, we see that sometimes. Caddy usually handles it fine, sometimes with a bit of massaging the config.

Rate limiting plugin: https://github.com/mholt/caddy-ratelimit

Unfortunately it still does not come with some good rate limiting oob, I found https://github.com/mholt/caddy-ratelimit which is "work in progress" only - not clear if that is ok for production. I really like the slickness of caddy, but I do not understand how a web server without rate limiting can be used for anything serious, you will need that for any website with some exposure. Not sure if anything else is missing in comparison to nginx, I stopped research at this first very important point. I think streaming would be my next item on the list of things that you might realize nginx is not that bad at...