Olric: Distributed, embeddable data structures in Go

I know Java and Erlang ecosystems have been big on this at times (Hazelcast, mnesia). When are these the appropriate architectural choice, if ever?<p>Definitely fun&#x2F;cool tech, I just don&#x27;t understand how pragmatic it is.

&gt; Olric v0.4 and previous versions use Olric Binary Protocol, v0.5 uses Redis serialization protocol for communication and the API was significantly changed. Olric v0.4.x tree is going to receive bug fixes and security updates forever, but I would recommend considering an upgrade to the new version.<p>Seems like a tall order to promise updates “forever”, particularly for a v0 release.

While it sounds interesting, I&#x27;m not sure in which scenario do I pick this over Redis

I don’t understand why anyone would pick the redis wire protocol.

Congrats Burak on making it to the main page!

I was excited to read its embeddable data structure then found it did Redis serialisation. I was hoping for something close to plasma store given that one isn’t getting much love these days. Would be great to get something that can save binary formats like arrow.

Relevant discussion when it comes to Redis compatible API: <a href="https:&#x2F;&#x2F;news.ycombinator.com&#x2F;item?id=31796311" rel="nofollow">https:&#x2F;&#x2F;news.ycombinator.com&#x2F;item?id=31796311</a>

I don’t understand why people need another abstraction layer on top of Redis? What can this do that Redis can’t?

olric. Great name :)