Limiter VS goralim

Fun weekend project but definitely not production-ready (no tests, no error handling, etc.). If readers are looking for something production-ready to use, consider https://github.com/go-redis/redis_rate (which implements GCRA/leaky bucket), or https://github.com/ulule/limiter (which uses a much simpler algorithm, but has good middleware).

If you're someone who loves to contribute to open-source projects, you're more than welcome to contribute to my project goralim. If this story of mine gave you a little bit of motivation to work on that stupid idea you've had, go work on it. Build it for yourself. And I would appreciate some stars too on my project.

Nice project, but for other readers, please don't use this in production. There is almost no error handling whatsoever going on: for example, see https://github.com/0verread/goralim/blob/main/goralim.go#L36. What happens if the redis calls in this function fail? If the Get here https://github.com/0verread/goralim/blob/main/goralim.go#L58 fails, for example if your redis connection dies, the code will always return false.

The code in the README will also result in a panic if the connection to the redis client fails.

Consider using https://github.com/go-redis/redis_rate (which implements leaky bucket/GCRA) or https://github.com/ulule/limiter (which implements a much more basic rate limiting algorithm, but has good middleware support) instead.