Olric: Distributed in-memory data structures in Go

Distributed in-process cache can make things very fast. See vimeo with group cache: <a href="https:&#x2F;&#x2F;medium.com&#x2F;vimeo-engineering-blog&#x2F;video-metadata-caching-at-vimeo-a54b25f0b304" rel="nofollow">https:&#x2F;&#x2F;medium.com&#x2F;vimeo-engineering-blog&#x2F;video-metadata-cac...</a><p>Or in-process distributed rate limiting: <a href="https:&#x2F;&#x2F;github.com&#x2F;mailgun&#x2F;gubernator" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;mailgun&#x2F;gubernator</a><p><a href="https:&#x2F;&#x2F;github.com&#x2F;golang&#x2F;groupcache" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;golang&#x2F;groupcache</a>: groupcache is in production use by dl.google.com (its original user), parts of Blogger, parts of Google Code, parts of Google Fiber, parts of Google production monitoring systems, etc.<p>There was also a paper by google that I can&#x27;t find right now.<p>Edit: Found it <a href="https:&#x2F;&#x2F;blog.acolyer.org&#x2F;2019&#x2F;06&#x2F;24&#x2F;fast-key-value-stores&#x2F;" rel="nofollow">https:&#x2F;&#x2F;blog.acolyer.org&#x2F;2019&#x2F;06&#x2F;24&#x2F;fast-key-value-stores&#x2F;</a>

Perhaps a better link would be the README which explains what&#x27;s the project about and its features.<p><a href="https:&#x2F;&#x2F;github.com&#x2F;buraksezer&#x2F;olric&#x2F;blob&#x2F;master&#x2F;README.md" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;buraksezer&#x2F;olric&#x2F;blob&#x2F;master&#x2F;README.md</a>

Very curious about the origins of this tool and how it is used by the creator. Looks very comprehensive, but some real world examples of use and performance would be great.

I have been curious about Olric for a while now.<p>* It is embeddable.<p>* Seems easy to install, even without Kubernetes.<p>I am just missing performance number to answer questions like: Is it significantly faster than etcd? Is it faster than tikv? And finally, is it faster than Redis Cluster?

Played around w&#x2F; olric a while back as a kv store for a routing graph, really enjoyed it even though I ended up home-brewing it later (the network topology meant that olric wasn’t the right tool for the job). Highly recommend it ;)

I’m curious how you actually would access this, would you need some kind of an RPC library to use in conjunction with it? The page doesn’t really seem to go far enough to answer actual usage information.<p>What would be the alternative to using a library like this? I’ve been looking for a good way to distribute workload to many machines and don’t want to invent it myself or jump into a very heavy system.

Reminds me of a stripped down version of Hazelcast.

Also discussed 6 months ago: <a href="https:&#x2F;&#x2F;news.ycombinator.com&#x2F;item?id=22297507" rel="nofollow">https:&#x2F;&#x2F;news.ycombinator.com&#x2F;item?id=22297507</a>

So would this be similar to Apache Ignite?

Looks like Hazelcast kind of solution.

Maybe just a personal thing, but going to a github repo and seeing &quot;build failing&quot; and low test coverage icons are usually turn offs for me to continue reading.

Love this idea, can’t wait to try it out!

Thanks man!