olric
Olric is a distributed, in-memory key-value store and cache written in Go that can run as an embedded library or standalone service. It uses the Redis protocol, supports automatic partitioning and replication, and is designed for fast data sharing across clusters.
Key facts
Objective fields from the source. Values we can't verify are shown as “Unknown” rather than guessed.
| Field | Value |
|---|---|
| Repository | olric-data/olric |
| Owner | olric-data |
| Primary language | Go |
| License | Apache-2.0 — OSI-approved |
| Stars | 3.5k |
| Forks | 147 |
| Open issues | 18 |
| Latest release | v0.7.4 (2026-06-12) |
| Last updated | 2026-06-26 |
| Source | https://github.com/olric-data/olric |
What olric is
Go-based distributed hash table offering RESP protocol compatibility, quorum-based replica control, eventual consistency (PA/EC), configurable eviction policies (LRU, TTL, MaxIdleDuration), and pub-sub messaging. Data is automatically sharded and rebalanced without external coordination.
Get the olric source
Clone the repository and explore it locally.
git clone https://github.com/olric-data/olric.gitcd olric# follow the project's README for install & configurationNeed it deployed, integrated, or customized instead? DEV.co ships production installs.
Best use cases
Implementation considerations
- Embedded library requires Go application; standalone server mode needs separate infrastructure and network coordination.
- Replication is synchronous by default but can be configured async—choose based on consistency vs. performance tradeoff.
- Quorum-based read/write voting adds latency; tune replica counts and quorum settings for your availability target.
- No built-in authentication by default; AUTH command exists but security posture requires verification for production use.
- Eviction policies (LRU, TTL) apply per-node; ensure memory limits align with cluster capacity for predictable behavior.
When to avoid it — and what to weigh
- Strict Consistency Required — Olric provides eventual consistency (PA/EC per PACELC). Not suitable for financial transactions or strict ACID requirements.
- Persistent Long-term Storage — In-memory only; no disk persistence. Data loss occurs on cluster failure. Use Redis or persistent databases for durability.
- Language-Agnostic Requirement on Embedded Mode — Embedded mode requires Go integration. Standalone service mode is available but adds operational complexity.
- Large-scale Horizontal Scaling Concerns — While claimed to handle hundreds of members, production validation at scale is not evident from public data.
License & commercial use
Apache License 2.0 (Apache-2.0). Permissive OSI-approved license allowing commercial use, modification, and distribution with minimal restrictions (license text and notice required).
Apache-2.0 is commercially safe for closed-source products and services. No license fees or commercial restrictions. However, verify your specific use case (embedded library vs. standalone service) and any proprietary modifications against Apache-2.0 obligations.
DEV.co evaluation signals
Editorial assessment — not user reviews. Directional, with an explicit confidence level.
| Signal | Assessment |
|---|---|
| Maintenance | Active |
| Documentation | Adequate |
| License clarity | Clear |
| Deployment complexity | Moderate |
| DEV.co fit | Good |
| Assessment confidence | High |
AUTH command is mentioned but not clarified as enabled by default. In-memory data is vulnerable to node compromise; encryption at rest and in transit not discussed. No audit logging or multi-tenancy isolation documented. Quorum voting provides some split-brain protection but is not a full Byzantine fault tolerance mechanism. Evaluate threat model and network isolation requirements before production use.
Alternatives to consider
Redis Cluster
Battle-tested, broader ecosystem, better documentation, persistent storage options (RDB, AOF). More mature for production use.
Memcached
Simpler, lower memory overhead for pure caching. No cluster coordination; suitable if eventual consistency and auto-sharding are not critical.
Apache Ignite
Full-featured distributed cache with SQL, compute grids, and persistence. More feature-rich but higher operational complexity.
Build on olric with DEV.co software developers
Review Olric's Apache-2.0 license, consistency guarantees, and cluster architecture. Assess production readiness and compare against Redis Cluster or Memcached for your use case.
Talk to DEV.coRelated on DEV.co
Explore the category and the services that help you build with it.
olric FAQ
Can Olric persist data to disk?
Is Olric production-ready?
How does Olric compare to Redis?
Can I use Olric in Kubernetes?
Custom software development services
DEV.co helps companies turn open-source tools like olric into production software. Our software development services cover the full lifecycle — architecture, web development, integration, and maintenance — delivered by software developers and web developers who ship. Engage our software development agency to implement or customize it for your open-source databases stack.
Evaluate Olric for Your Distributed Caching Needs
Review Olric's Apache-2.0 license, consistency guarantees, and cluster architecture. Assess production readiness and compare against Redis Cluster or Memcached for your use case.