Didn't Discord have issues when they did caching in Go due to the garbage collector having to run over all objects ever 2 minutes? Was that resolved in a newer version of Go or does this project get around that problem in another way?
Brad Fitzpatrick and others pointed out that in that article they were using Go 1.6, but the garbage collector got way better since then and it would be possible that just upgrading Go would have solved the issue for them.
Ah, as I understood it the Discord issues only shows up when you do a large long term map(? -> object) but maps with primitive values don't trigger it.
Olric is an in-memory and distributed key/value store. Bolt is an b-tree based on-disk key/value store and it's not distributed. Olric can be compared with https://github.com/golang/groupcache and it's highly inspired by Amazon DynamoDB paper and Hazelcast.
Olric is not Redis. Redis implements different data structures and has different persistence options. Olric only provides a key/value store and it's suitable to be used as a distributed cache. README.md file contains enough information to compare those tools.
