awesome-repositories.com
Blog
MCP
awesome-repositories.com

Discover the best open-source repositories with AI-powered search.

ExploreCurated searchesOpen-source alternativesSelf-hosted softwareBlogSitemap
ProjectMCP serverAboutHow we rankPress
LegalPrivacyTerms
© 2026 Bringes Technology SRL·VAT RO45896025·hello@awesome-repositories.com
nalgeon avatar

nalgeon/redka

0
View on GitHub↗
4,555 stars·130 forks·Go·BSD-3-Clause·9 views

Redka

Redka is a SQL-backed key-value store that implements a Redis-compatible interface. It acts as a relational data bridge, translating non-relational protocol commands into relational queries to provide persistence and ACID transactions using a SQL database backend.

The system allows for relational data introspection by exposing internal key-value data as SQL views, enabling direct querying and analysis via relational syntax. It can be deployed as a standalone network server or as an embedded library within a Go application.

The project supports a variety of data structures, including strings, lists, hashes, unordered sets, and sorted sets. It provides capabilities for key lifecycle management with time-to-live metadata, atomic numeric operations, and set algebra. To manage performance and access, it includes an in-memory storage mode and a read-only connection mode.

Features

  • Redis Compatible Stores - Implements a Redis-compatible API interface that allows the store to be used with standard Redis clients.
  • Redis-Compatible Implementations - Implements a Redis-compatible API interface that translates non-relational commands into relational SQL queries.
  • ACID Transactional Cores - Leverages the underlying relational database engine to provide ACID compliant transactions for grouped operations.
  • Atomic Transaction Execution - Leverages the underlying relational database engine to ensure ACID compliance for grouped data operations.
  • SQL-Backed Stores - Uses a SQL database as the primary persistence layer to store non-relational data structures.
  • Relational Storage Backends - Uses a relational database as the primary persistence layer for storing key-value data structures.
  • Relational Data Introspection - Exposes internal key-value data as SQL views to enable direct querying and analysis via relational syntax.
  • Relational Database Integrations - Bridges Redis protocol operations with SQL storage to combine high-speed access with relational durability.
  • Embedded Key-Value Stores - Integrates a key-value data layer directly into an application process as an embedded library.
  • Protocol Translation - Translates Redis wire protocol commands into corresponding relational SQL queries for storage and retrieval.
  • Key Expiration Management - Stores expiration timestamps within the database to automate the cleanup of expired key-value pairs.
  • In-Process Library Modes - Allows the server to run in-process within a Go application to provide functionality without a separate process.
  • Hash Maps - Supports Redis-style hash maps for storing and manipulating field-value pairs.
  • Key Lifecycle Management - Manages key lifecycles by setting and querying expiration timers for automatic data cleanup.
  • List Data Structures - Implements ordered list operations, such as pushing and popping elements, for data sequence management.
  • Data Introspection Views - Exposes internal key-value data as SQL views to enable direct querying and analysis via relational syntax.
  • Relational Data Bridges - Maps non-relational data structures like sets and hashes to relational tables and views for easier analysis.
  • Analysis Views - Provides relational views over stored key-value data to simplify reporting and introspection.
  • Sorted Sets - Stores unique strings associated with numeric scores to enable retrieval by rank or score range.
  • String Value Assignments - Stores and retrieves byte sequences by key using single or batch updates and retrieval.
  • Unordered Unique Collection Management - Stores and manipulates unordered sets of unique strings with membership checking and modification.
  • Embedded and Standalone Modes - Provides the flexibility to deploy as a standalone network server or as an embedded Go library.
  • Set Operations - Computes the intersection, union, and difference between multiple sets and stores the resulting set.
  • Atomic Integer Operations - Provides thread-safe atomic increments and decrements for integer and floating-point values stored at specific keys.
  • Standalone Server Modes - Supports running as a standalone network server process for independent deployment.
  • Database Engines - Redis re-implemented on top of SQLite.
  • Database Systems - Listed in the “Database Systems” section of the Awesome Go awesome list.

Star history

Star history chart for nalgeon/redkaStar history chart for nalgeon/redka

How this analysis was created: This summary and feature list are AI-generated from collected project material and can contain mistakes. Stars, license and language are imported from GitHub. Inclusion does not mean that we have tested or audited this project. Check the source documentation for any feature you depend on. Learn more on our About page.

AI search

Explore more awesome repositories

Describe what you need in plain English — the AI ranks thousands of curated open-source projects by relevance.

Start searching with AI

Frequently asked questions

What does nalgeon/redka do?

Redka is a SQL-backed key-value store that implements a Redis-compatible interface. It acts as a relational data bridge, translating non-relational protocol commands into relational queries to provide persistence and ACID transactions using a SQL database backend.

What are the main features of nalgeon/redka?

The main features of nalgeon/redka are: Redis Compatible Stores, Redis-Compatible Implementations, ACID Transactional Cores, Atomic Transaction Execution, SQL-Backed Stores, Relational Storage Backends, Relational Data Introspection, Relational Database Integrations.

Which projects share features with nalgeon/redka?

Projects with overlapping indexed features include: apache/incubator-kvrocks — Kvrocks is a disk-based NoSQL database and distributed key-value store that leverages the RocksDB storage engine to… hdt3213/godis — Godis is a Redis-compatible in-memory database and distributed key-value store. It functions as a replicated data… microsoft/garnet — Garnet is a multi-threaded in-memory database and distributed key-value store. It functions as a high-performance… nutsdb/nutsdb — NutsDB is an ACID-compliant, embedded transactional storage engine that functions as both a disk-backed key-value… etcd-io/bbolt — bbolt is an ACID-compliant embedded key-value store for Go applications. It persists all data in a single… tporadowski/redis — Redis is a high-performance in-memory key-value store that functions as a distributed cache, message broker, and NoSQL…

Projects sharing features with Redka

These projects share indexed features with Redka. Shared tags can include platform or build tooling; verify the primary use case before treating a result as a replacement.
  • apache/incubator-kvrocksapache avatar

    apache/incubator-kvrocks

    4,339View on GitHub↗

    Kvrocks is a disk-based NoSQL database and distributed key-value store that leverages the RocksDB storage engine to persist large datasets to physical disk. It is designed to be a Redis-compatible database, utilizing the standard Redis communication protocol to ensure interoperability with existing client libraries and tools. The project distinguishes itself by combining a disk-persistent storage model with advanced retrieval capabilities, including vector search for k-nearest neighbor queries, full-text search indexing, and geospatial query execution. It supports distributed clustering with

    C++
    View on GitHub↗4,339
  • hdt3213/godisHDT3213 avatar

    HDT3213/godis

    3,836View on GitHub↗

    Godis is a Redis-compatible in-memory database and distributed key-value store. It functions as a replicated data store and distributed message broker, implementing the Redis protocol to manage complex data structures in memory. The system provides a geospatial indexing engine for proximity-based queries and distance calculations. It ensures high availability and data durability through master-slave replication and write-ahead logging. The project covers a wide range of capabilities including the management of strings, hash maps, lists, and sorted sets. It supports distributed data clusterin

    Goclustergogodis
    View on GitHub↗3,836
  • microsoft/garnetmicrosoft avatar

    microsoft/garnet

    11,885View on GitHub↗

    Garnet is a multi-threaded in-memory database and distributed key-value store. It functions as a high-performance remote cache store that implements the RESP wire protocol to maintain compatibility with existing Redis clients and libraries. The project is distinguished by a shared-memory architecture that enables parallel request processing across multiple cores for sub-millisecond latency. It features a tiered storage system that automatically offloads colder data from system memory to SSD or cloud storage layers, and includes a specialized vector search database for high-dimensional similar

    C#cachecache-storagecluster
    View on GitHub↗11,885
  • nutsdb/nutsdbnutsdb avatar

    nutsdb/nutsdb

    3,554View on GitHub↗

    NutsDB is an ACID-compliant, embedded transactional storage engine that functions as both a disk-backed key-value store and an in-memory data structure store. It provides atomic and serializable transactions with commit and rollback capabilities to ensure strict data consistency for applications requiring a lightweight persistence layer. The engine distinguishes itself by supporting a variety of complex data types, including lists, sets, and sorted sets, alongside standard byte-slice storage. It implements a transactional storage model featuring hot backups and a compaction algorithm to maint

    Godata-structuresdatabasego
    View on GitHub↗3,554
Compare all 30 related projects→