gem-hunter

Redka reimplements the core parts of Redis with SQL, while remaining compatible with Redis API.

Highlights:

• Data doesn't have to fit in RAM.
• Supports ACID transactions.
• SQL views for easier analysis and reporting.
• Uses SQLite or PostgreSQL as a backend.
• Runs in-process (Go API) or as a standalone server.
• Implements Redis commands and wire protocol (RESP).

Redka is stable and ready to use for testing and non-critical production scenarios. It's currently in maintenance mode, and no new features are planned.

Here are some situations where Redka might be helpful:

Embedded cache for Go applications. If your Go app already uses SQLite or just needs a built-in key-value store, Redka is a natural fit. It gives you Redis-like features without the hassle of running a separate server. You're not limited to just get/set with expiration, of course — more advanced structures like lists, maps, and sets are also available.

Lightweight testing environment. Your app uses Redis in production, but setting up a Redis server for local development or integration tests can be a hassle. Redka with an in-memory database offers a fast alternative to test containers, providing full isolation for each test run.

Postgres-first data structures. If you prefer to use PostgreSQL for everything but need Redis-like data structures, Redka can use your existing database as the backend. This way, you can manage both relational data and specialized data structures with the same tools and transactional guarantees.

Redka supports five core Redis data types:

• Strings are the most basic Redis type, representing a sequence of bytes.
• Lists are sequences of strings sorted by insertion order.
• Sets are unordered collections of unique strings.
• Hashes are field-value (hash)maps.
• Sorted sets (zsets) are collections of unique strings ordered by each string's associated score.

Redka also provides commands for key management, server/connection management, and transactions.

Redka comes in two flavors:

• Standalone Redis-compatible server: installation, usage.
• Go module for in-process use: installation, usage.

You can also run an in-process Redka server as a lightweight alternative to Redis test containers, or as a small-scale production instance.

Redka can use either SQLite or PostgreSQL as its backend. It stores data in a relational database with a simple schema and provides views for better introspection.

Redka is not about raw performance. You can't beat a specialized data store like Redis with a general-purpose relational backend like SQLite. However, Redka can still handle tens of thousands of operations per second, which should be more than enough for many apps.

See the benchmarks for more details.

Contributions are welcome. For anything other than bugfixes, please first open an issue to discuss what you want to change.

Make sure to add or update tests as needed.

Redka would not be possible without these great projects and their creators:

• Redis (Salvatore Sanfilippo). It's such an amazing idea to go beyond the get-set paradigm and provide a convenient API for more complex data structures.
• SQLite (D. Richard Hipp). The in-process database powering the world.
• Redcon (Josh Baker). A very clean and convenient implementation of a RESP server.

Logo font by Ek Type.

Redka is mostly a one-man project. It's currently in maintenance mode, and no new features are planned.