# olric-data/olric

Distributed, in-memory key/value store and cache. It can be used as an embedded Go library and a language-independent service.

Repository: https://github.com/olric-data/olric
Canonical: https://ross.abutalabs.com/products/olric
Language: Go
License: Apache-2.0
License Family: permissive
Topics: key-value-store, cache, distributed-database, key-value, distributed-cache, distributed-hash-table, database, redis, distributed-systems, in-memory-database, nosql, in-memory
Last push: 2026-08-20T18:34:18+00:00

## Health v2 (maintenance only)
Score: 91/100 (v2, computed 2026-09-03T02:20:16.233290+00:00)
- activity 98, release rhythm 76, longevity 100
- inputs: {"age_days": 3072, "days_push": 13, "days_rel": 82, "gap_med": 64, "n_releases_24m": 8}
- flags: none
- formula: round(0.45*activity + 0.35*rhythm + 0.20*longevity); archived -> min(score, 10)

## Adoption (not part of the score)
Stars 3490, forks 150 (observed 2026-08-28T04:08:07.169940+00:00)

## What it is
Olric is a distributed, in-memory key/value store and cache written entirely in Go. It can be embedded as a Go library or run as a standalone language-independent service, speaking the Redis serialization protocol (RESP).

## Use cases
- distributed caching across a cluster of servers
- sharing transient fast-changing data between application instances
- managing cluster state for distributed applications
- drop-in replacement for Redis pub/sub messaging
- scaling an in-memory data pool horizontally without external coordination
- embedding a key/value cache directly into a Go application

## When to choose
- you need a scalable shared cache pool across many machines in Go
- you want Redis-protocol compatibility without running Redis
- you need automatic sharding and rebalancing with no external coordination service
- you want an embeddable distributed cache library

## When to avoid
- you need durable on-disk persistence of data
- you need full Redis feature set like transactions, Lua scripting, or rich data structures
- your dataset is small enough for a single Redis or in-process cache
- you need a mature 1.0 production-hardened release

## Facets
- artifact type: library
- maturity: active
- function: caching, database, message-queue, serialization
- domain: databases, microservices, developer-tools
- platform: go, cross-platform, self-hosted
- tags: key-value-store, distributed-cache, in-memory-database, distributed-hash-table, redis-protocol, resp, pub-sub, sharding, nosql, embedded, caching, docker

## Member repositories
- olric-data/olric (main) score 91

## Provenance
- Observed fields: from GitHub, fetched 2026-08-28T04:08:07.169940+00:00.
- Health v2: computed from the inputs above; adoption is never an input.
- Inferred fields (summary, facets, guidance): AI-extracted, prompt v1, taxonomy v1, on 2026-08-29T18:35:57.990043+00:00, confidence not recorded.
  - readme: https://github.com/olric-data/olric (fetched 2026-08-28T04:08:07.169940+00:00, sha d4fa48444747)
- Data as of 2026-08-30T08:39:29.467469+00:00.