yogeshpandey

6 ms·

1. 1.▲
   by yogeshpandey 8y ago

   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
2. 2.▲
   by yogeshpandey 8y ago

   Yes that's what I meant. The best size from Ipv4 is 4 bytes. Its better instead of using 111.111.111.111
3. 3.▲
   by yogeshpandey 8y ago

   absolutely right, Unix sockets are quite faster than even loopback tcp connections. We have plan to introduce that in roadmap. But to start with we wanted to cover general usecases first. Http interface also make it platform independent.
4. 4.▲
   by yogeshpandey 8y ago

   Can you please elaborate more on the usecase
5. 5.▲
   by yogeshpandey 8y ago

   Agree with this. Space used by keys can be reduced by hashing the key. Or for IPs they can be converted to an int value.
6. 6.▲
   by yogeshpandey 8y ago

   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 globa
7. 7.▲
   by yogeshpandey 8y ago

   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.
8. 8.▲
   by yogeshpandey 8y ago

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