foundationdb vs tidesdb
Distributed transactional storage compared
foundationdb is a distributed ordered key-value database that provides ACID transactions across clusters. tidesdb is an embeddable C storage-engine library; the main distinction is a database component designed for cluster-wide use versus a library integrated into an application.
foundationdb: Store Data Reliably Across Distributed Clusters
FoundationDB is a distributed ordered key-value database with ACID transactions, built for structured data across clusters of commodity servers. It suits applications that need transactional correctness and flexible language bindings.
tidesdb: Transactional LSM-Tree Storage Engine in C
TidesDB is a C library for transactional key-value storage built on an LSM-tree, with a hybrid B-tree design. It is intended for embedding in applications or using as a standalone key-value or column store, and supports Linux, macOS, Windows, and other platforms.
| foundationdb | tidesdb | |
|---|---|---|
| Language | C++ | C |
| License | Apache-2.0 | MPL-2.0 |
| Stars | 16.7k | 602 |
| Forks | 1.6k | 59 |
| Last analyzed | Oct 3, 2026 | Oct 22, 2026 |
Key differences
- foundationdb stores ordered key-value data across clusters of commodity servers; tidesdb is an embedded storage engine using a hybrid LSM and B-tree design.
- foundationdb is written in C++ and offers language bindings; tidesdb is a C library whose API applications integrate directly.
- foundationdb provides ACID transactions for all operations; tidesdb describes MVCC, five isolation levels, and configurable durability.
- foundationdb is licensed under Apache-2.0; tidesdb uses MPL-2.0, with additional licenses applying to dependencies.
- foundationdb's production release guidance identifies 7.3 as the supported branch; tidesdb's supplied information describes cross-platform support across several operating systems and processor architectures.
- foundationdb suits applications seeking a transactional database foundation; tidesdb targets developers embedding storage or building a database or column-store layer.
Choose foundationdb if you…
- need ordered key-value storage and ACID transactions across distributed clusters.
- want language bindings for integrating a transactional storage foundation into an application.
- need a database component for read/write or write-intensive workloads across servers.
Choose tidesdb if you…
- want to embed a transactional key-value or column-family storage engine in a C application.
- need features such as ordered range scans, range deletes, or configurable durability and compression.
- are building a database or storage system and want to use a library rather than adopt a full database server.
Compare the numbers side by side, or add more projects
This comparison is generated with AI from the OSRepos analyses of both projects. Always check each project's repository and documentation before choosing.