olric is queued for analysis. Crawling candidates and ranking them takes a few minutes. This page updates itself when the list exists — you can also come back later.
What is known so far comes from the other direction:
These projects were analysed and named olric among their alternatives. The relationship is not symmetric — how olric rates them is a separate judgement, made when olric is analysed in its own right.
calls olric “Choose when you want an embedded/distributed Go cache without Redis protocol compatibility.”
For developers, who are building real-time data-driven applications, Redis is the preferred, fastest, and most feature-rich cache, data structure server, and document and vector query engine.
calls olric “choose when you want a Go-native distributed cache that can be embedded as a library or run as a standalone service.”
A flexible distributed key-value database that is optimized for caching and other realtime workloads.
calls olric “choose for an embedded Go distributed cache with its own protocol when you don't need Redis wire compatibility”
Garnet is a remote cache-store from Microsoft Research that offers strong performance (throughput and latency), scalability, storage, recovery, cluster sharding, key migration, and replication features. Garnet can work with existing Redis clients.
calls olric “choose when you want a lightweight Go-embeddable distributed in-memory cache instead of a Java platform with stream processing.”
Hazelcast is a unified real-time data platform combining stream processing with a fast data store, allowing customers to act instantly on data-in-motion for real-time insights.