olric-data/olric

Health v2 · maintenance only

Adoption not part of the score

3490 stars · 150 forks observed · 2026-08-28

What it is AI-extracted, prompt v1, taxonomy v1, 2026-08-29, confidence not recorded

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

library · maturity active

caching database message-queue serialization databases microservices developer-tools go cross-platform self-hosted key-value-store distributed-cache in-memory-database distributed-hash-table redis-protocol resp pub-sub sharding nosql embedded caching docker

Member repositories

For agents

markdown · JSON · MCP: product_card(name="olric-data/olric")