nalgeon/redka

Health v2 · maintenance only

Adoption not part of the score

4567 stars · 135 forks observed · 2026-09-22

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

Redka reimplements the core parts of Redis (strings, lists, sets, hashes, sorted sets) on top of SQL backends like SQLite or PostgreSQL, while remaining compatible with the Redis API and wire protocol. It can run as a standalone Redis-compatible server or as an in-process Go module.

Use cases

• embedded key-value cache for Go applications without running a separate Redis server
• lightweight Redis replacement for local development and integration tests
• in-memory database alternative to Redis test containers
• Redis-like data structures backed by an existing PostgreSQL database
• querying key-value data with SQL views for analysis and reporting
• ACID-transactional key-value store for data that doesn't fit in RAM

When to choose

• your Go app needs Redis-like features embedded in-process
• you want Redis semantics with durable, disk-backed SQL storage
• you need a fast, isolated Redis stand-in for testing
• you prefer managing everything in PostgreSQL with transactional guarantees

When to avoid

• you need raw Redis performance or very high throughput
• you rely on Redis features beyond the five core data types (pub/sub, streams, etc.)
• you need actively developed new features, since the project is in maintenance mode
• you need a battle-tested store for critical production workloads

Facets

library · maturity maintenance

database caching http-server databases developer-tools backend go cross-platform cli self-hosted redis-compatible sqlite postgresql key-value-store resp-protocol embedded-database

Member repositories

For agents

markdown · JSON · MCP: product_card(name="nalgeon/redka")