Show HN: Golimit – Ringpop-based distributed and decentralized rate limiter (opens in new tab)

Sadly ringpop is no more active. But in golimit we are using just clustering constructs of ringpop, which seems to be quite stable in latest version.

We are using distributed counter for rate calculation. Every node stores a local and global counter value. Rate limit is applied on local+global value. The local value is synced periodically on configured interval or when local counter threshold exceeds a configured threshold value.

Totally biased opinion, but I think you should check out https://github.com/mokies/ratelimitj if you are Java based.

Golimit tries to reuse the allocated keys counter entry in case the counter has expired and its not collected by GC. There is a very simple GC logic where GC is invoked periodically, and scans for all buckets one by one and cleans them up. The GC invocation frequency can be configured by setting "gcinterval" property in yaml.

If it is rate limiting IPv4 address space, then you only need a few gigs to store them all... perhaps this is why there is no garbage collection.

Why is it impossible, maybe just not useful? Otherwise you can use CRDTs for connection counters and maybe exclude counters that are lagging behind too much.

Can you please elaborate more on the usecase

you can write LUA code in Haproxy to call golimit on http endpoint. and react based on response

Thanks, The counters are synced in CRDT way , every node has both local and global counters and local counter are synced asynchronously with global counter periodically or on certain events. Usually the rates would be defined in a period of few minutes or seconds. So after the window is over the counter value will vanish automatically. so making counter durable seems unnecessary overhead as of now. But durability can be added in project if the need comes