Go and a not tiny amount of memory
hackernoon.com
hackernoon.com
[1] https://github.com/coocood/freecache [2] https://github.com/allegro/bigcache
Also funny that they admit the CPU use might not really be a problem... but try to solve it anyway and add a lot of complexity to their system.
I have learned to KISS and am I am surprised they are solving this problem and don't have more pressing product development. Doing something like this is pretty standard, but doing it before its needed smells of misused engineering time.
Also they didn't even really need to do most of the work they did here, they could have re-used existing out-of-heap Go memory mgmt solutions like: https://github.com/teh-cmc/mmm . But I get it, building things is fun :) But like the parent said, I'd expect it to be a personal rather than a company project.
Why not use one of the many full-featured RDBMS or KV stores available for free?
This is an already solved problem. Go isn't the best tool for all cases.
If someone is wrong or ignorant, teach them something. Then we all learn. Alternatively, it's fine not to comment.
I shouldn't be surprised. The red flag was flying as soon as IOP was used in singular form.
Input/Output Operations Per.
> Input/Output Per.
IOPS can also be "I/O operations per second" and in that context "1 IOP" is a meaningful quantity.
Particularly when AWS and other cloud providers sell capacity in units of IOPS: https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ebs-io-c...