It would be useful for keter to implement rate limiting, perhaps taking inspiration from an established design such as [rack-attack][0]. This may help mitigate issue like [this one][1], where the solution is to rely on rate limiting in nginx. [0]: https://github.com/rack/rack-attack [1]: https://github.com/snoyberg/keter/issues/245
It would be useful for keter to implement rate limiting, perhaps taking inspiration from an established design such as rack-attack.
This may help mitigate issue like this one, where the solution is to rely on rate limiting in nginx.