For developers, who are building real-time data-driven applications, Redis is the preferred, fastest, and most feature-rich cache, data structure server, and document and vector query engine.
Repository Index
47,133 repositories indexed
1–18 of 18 · Most stars
A flexible distributed key-value database that is optimized for caching and other realtime workloads.
immudb - immutable database based on zero trust, SQL/Key-Value/Document model, tamperproof, data change history
- key-value
- immutable
- merkle-tree
- go
Redis re-implemented with SQL
TranslatedA Golang implemented Redis Server and Cluster.
- kv-cache
- golang
- redis-server
- redis
A simple, fast, embeddable, persistent key/value store written in pure Go. It supports fully serializable transactions and many data structures such as list, set, sorted set.
jStorage is a simple key/value database to store data on browser side
Aerospike Database Server – flash-optimized, in-memory, nosql database
moss - a simple, fast, ordered, persistable, key-val storage library for golang
High-performance write & space optimized transactional storage engine.
- storage-engine
- c-library
- database
- lsm-tree
C# .NET NOSQL ( key value, object store embedded TextSearch SemanticSearch Vector layer ) ACID multi-paradigm database management system.
A high performance, shared memory, lock free, cross platform, single file, no dependencies, C++11 key-value store
An Erlang implementation of Redis
Fast and simple key/value store written using Go's standard library
In-memory key-value server in Rust that speaks RESP, so redis-cli and Redis clients connect. Locks, rate limits, job queues and a change feed are single commands; Raft-based failover. Clients for Rust, .NET, Go, Java, Python and Node.js.
An implementation of the Raft distributed consensus protocol, verified in Coq using the Verdi framework
- raft
- verdi
- coq
- proof
LibraDB is a simple, persistent key/value store written in pure Go in less than 1000 lines for learning purposes.
- data-structures
- database
- go
- golang
Simply ACID* key-value database. At the medium or even low latency it tries to provide greater throughput without losing the ACID properties of the database. The database provides the ability to create record headers at own discretion and use them as transactions. The maximum size of stored data is limited by the size of the computer's RAM.