Implement a rate limiting mechanism

[jezen]

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.

[jappeace]

Data.Cache could be used as an internal "redis" to help detect request spamming.

[alexbiehl]

It looks like there’s a rate limiting plugin available for keter: https://hackage.haskell.org/package/keter-rate-limiting-plugin-0.1.1.0

[jezen]

Yes. I believe the plan is to fold that work into this package. It should be packaged and configured similar to the PostgreSQL plugin which is included with keter.

[jappeace]

You should coordinate with the maintainer of that plugin because they're active.

[jezen]

I am indeed coordinating with Oleksandr 🙂

[jappeace]

Actually, that's a bunch of AI generated code. Wouldn't it be better to just keep that separate for now?
I'd rather not merge another not invented here cache implementation. Or all those custom typeclasses, lack of newtype usage etc.

[jezen]

Sorry, let me clarify.

The plan is to fold the rate limiting mechanism into this package, but without a NIH cache implementation, and without any AI slop. We want that behaviour, but we also want the code in this project to get better over time.

We should not merge that package here as it exists currently.