Distributed transactional key-value database, originally created to complement TiDB
- distributed-transactions
- raft
- rust
- key-value
94,845 visible repositories in the index
1–17 of 17 · Most stars
Distributed transactional key-value database, originally created to complement TiDB
FoundationDB - the open source, distributed, transactional key-value store
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.
An Embedded NoSQL, Transactional Database Engine
Zedis: A blazing-fast, native Redis GUI built with Rust and GPUI.
Modern transactional key-value/row storage library.
High Performance Redis-API Compatible Distributed Database with Persistency, Scalability, Full ACID Transactions, and Tiered S3 Storage Cost Efficiency
Fastfull embedded transactional key-value storage engine ★ Surpasses the legendary LMDB in reliability, capabilities and performance ★ Used in hundreds of open source projects, including Ethereum.
Distributed transactional NoSQL database, Redis protocol compatible using tikv as backend
Transactional schema-less embedded database used by JetBrains YouTrack and JetBrains Hub.
Elixir embedded key/value database
Embedded transactional database for blobs, documents & graphs, with kernel-bypass NVMe through io_uring & SPDK, GPU compaction, and one C ABI over its own, RocksDB & LevelDB engines 🗄️
High-performance write & space optimized transactional storage engine.
C# .NET NOSQL ( key value, object store embedded TextSearch SemanticSearch Vector layer ) ACID multi-paradigm database management system.
ZoneTree is a persistent, high-performance, transactional, ACID-compliant ordered key-value database and LSM-tree storage engine for .NET.
The DB that's replicated, sharded and transactional.
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.