For a relational database management system for developers, the strongest matches are cockroachdb/cockroach (CockroachDB is a distributed SQL database that provides ACID), erikgrinaker/toydb (ToyDB is an open-source distributed SQL database that provides) and postgres/postgres (PostgreSQL is the reference open-source relational database, providing ACID). pingcap/tidb and timescale/timescaledb round out the shortlist. Each is ranked by relevance to your query, popularity and recent activity.
Open-source utilities for managing, monitoring, optimizing, and interacting with PostgreSQL database clusters and schemas.
Cockroach is a distributed SQL database designed to scale horizontally across multiple nodes while maintaining strict ACID compliance and global data consistency. It functions as a relational database engine that automatically partitions data into ranges, rebalancing them across a cluster to accommodate growing storage and throughput requirements. By utilizing a distributed consensus protocol, the system ensures that all nodes agree on the order of operations, providing fault tolerance and continuous availability even in the event of hardware failures. The system distinguishes itself through
CockroachDB is a distributed SQL database that provides ACID transactions, MVCC, indexing, integrity constraints, replication, and point-in-time recovery, making it a strong relational database comparable to PostgreSQL for this search.
ToyDB is a distributed SQL database that provides a system for storing and querying data across multiple nodes. It focuses on maintaining strong consistency and fault tolerance through the implementation of a distributed consensus algorithm. The project distinguishes itself by supporting historical data versioning, enabling time-travel queries to retrieve the state of the database from a specific point in the past. It utilizes multi-version concurrency control to manage ACID transactions and ensure data integrity during concurrent operations. The system covers relational data modeling with t
ToyDB is an open-source distributed SQL database that provides ACID transactions, MVCC concurrency, time-travel queries for point-in-time recovery, and replication via distributed consensus, fitting the relational database management system category, though it is an experimental project rather than a production-grade equivalent of PostgreSQL.
PostgreSQL is an object-relational database management system designed for the persistent storage and retrieval of structured information. It functions as an ACID-compliant database server, utilizing standard query language protocols to maintain data consistency and reliability across large-scale application datasets. The system distinguishes itself through an extensible architecture that allows for the definition of custom data types, operators, and indexing methods. It employs multi-version concurrency control to enable simultaneous read and write operations without blocking, supported by a
PostgreSQL is the reference open-source relational database, providing ACID transactions, MVCC, SQL, indexing, data integrity constraints, write-ahead logging for point-in-time recovery, replication, and extensible custom types and operators—matching every required feature.
TiDB is a horizontally scalable, distributed SQL database designed to provide consistent transactional storage and high-performance analytical processing within a single unified architecture. It utilizes a decoupled compute-storage design and a distributed key-value storage layer to ensure horizontal scalability and efficient range-based queries. By employing a consensus-based replication algorithm, the system maintains high availability and automatic failover across multiple nodes and geographical regions. The platform distinguishes itself through its hybrid transactional and analytical proc
TiDB is a horizontally scalable distributed SQL database that supports SQL, ACID transactions, MVCC, indexing, and replication—covering the core RDBMS features you need—but it is MySQL-compatible rather than PostgreSQL, which may be a mismatch if you specifically require PostgreSQL compatibility.
TimescaleDB is an open-source PostgreSQL extension that adds native time-series capabilities to the database. At its core, it transforms standard PostgreSQL tables into hypertables—automatically partitioned by time intervals—so data is stored in fixed-size chunks without manual sharding. The extension includes a library of over 200 built-in SQL functions purpose-built for time-series workloads, such as time bucketing, gap filling, percentile estimation, and time-weighted averages. What distinguishes TimescaleDB from generic PostgreSQL is its set of integrated time-series features that work th
TimescaleDB is a PostgreSQL extension that inherits PostgreSQL's full SQL, ACID, MVCC, indexing, constraints, replication, and point-in-time recovery, so it functions as a relational database management system—but its core identity is a time-series specialization, making it a narrower fit than a general-purpose RDBMS.
redb is an embedded key-value store and ACID-compliant storage engine. It functions as a persistent storage system for saving and retrieving data as key-value pairs within a tree structure. The engine is built as an MVCC transactional database, utilizing multi-version concurrency control to manage simultaneous reads and writes without blocking. It employs a single-writer multi-reader model to ensure data consistency while allowing multiple threads to access the store. The system provides persistent state management and atomic transaction management to prevent data corruption during crashes.
Redb is an embedded key-value store with ACID transactions and MVCC, not a relational database—it stores key-value pairs in a B-tree rather than supporting SQL, tables, schemas, or relational integrity constraints, so it is a different class of storage engine from what this search requires.
KeyDB is a multithreaded in-memory key-value store and distributed cache. It functions as a NoSQL database utilizing multi-version concurrency control to execute non-blocking queries and scans. The project is a multithreaded fork of Redis that maintains protocol compatibility while utilizing a multithreaded architecture to scale across multi-core hardware. It distinguishes itself with flash-tiered storage, allowing the system to offload data from primary RAM to SSD or flash storage to increase total capacity. The system supports high availability through active-active mesh replication and mu
KeyDB is a multithreaded NoSQL key-value store based on Redis, not a relational database system with SQL query support, ACID transactions, or the relational features you need.
CloudNativePG is a Kubernetes operator designed for the administration, lifecycle management, and high availability of PostgreSQL database clusters. It functions as a declarative orchestrator that manages database instances through custom resources and manifests. The project distinguishes itself by automating complex operational tasks, including primary election and failover management via streaming physical replication. It provides specialized tools for database version migrations, supporting both offline in-place upgrades and online migrations through logical replication. The operator cove
CloudNativePG is a Kubernetes operator for managing PostgreSQL clusters, not the relational database engine itself — it automates operations but does not provide the core SQL database you are looking for.
MapDB is an embedded database engine and disk-backed collection library that stores Java collections on disk or off-heap. It functions as a local data processing engine designed to handle datasets that exceed available physical RAM. The project utilizes off-heap data storage to eliminate garbage collection overhead and employs disk overflow caching to balance memory and disk usage. It provides specialized utilities for filtering and analyzing large volumes of local data on a single machine. The system ensures data integrity through ACID-compliant transactions and multi-version concurrency co
MapDB is an embedded Java database engine with ACID transactions and MVCC, but it is a key-value/collection store, not a relational database with SQL query support, so it does not match the request for a PostgreSQL-like relational DBMS.
Vitess is a database clustering system for horizontal scaling of MySQL. It functions as a middleware layer that abstracts complex sharding and physical topology, allowing applications to interact with a distributed database environment through a unified interface. By intercepting and routing SQL queries across multiple shards, it enables large-scale data management while maintaining the appearance of a single database instance. The platform distinguishes itself through its ability to perform online schema migrations and distributed transaction coordination without requiring application downti
Vitess is a database clustering and sharding middleware for MySQL, not a standalone relational database management system—it lacks the core identity of providing ACID, MVCC, and point-in-time recovery as a primary database engine.
Sled is an embedded key-value store and ACID-compliant database designed for high-performance data persistence. It functions as a log-structured storage engine that organizes data using B+ trees to support efficient range queries and prefix scans. The engine implements a zero-copy data store model, utilizing epoch-based reclamation to provide direct references to cached values without memory allocations. It distinguishes itself through a combination of write-ahead logging, page cache optimizations to reduce write amplification on flash storage, and serializable transactions for atomic multi-k
Sled is an embedded ACID-compliant key-value store with B+ tree indexing, not a relational database management system—it lacks SQL query support, MVCC, data integrity constraints, point-in-time recovery, and the relational model you need.
Drift is a type-safe SQL persistence library and relational mapper that provides a structured way to map database tables to classes and execute SQL queries with build-time validation. It functions as a type-safe query builder and a wrapper for SQLite and PostgreSQL, eliminating manual result set parsing by binding query outputs to native objects. The project distinguishes itself through a build-time code generation system that produces type-safe APIs and validates raw SQL statements against database versions before execution. It features reactive query streaming, which transforms SQL queries
Drift is a type-safe persistence library and ORM for Dart/Flutter that wraps SQLite and PostgreSQL, not a relational database management system itself — it helps you query an existing RDBMS rather than providing the server-side storage, ACID guarantees, or replication you asked for.
| Repository | Stars | Language | License | Last push |
|---|---|---|---|---|
| cockroachdb/cockroach | 32.2K | Go | NOASSERTION | |
| erikgrinaker/toydb | 7.3K | Rust | Apache-2.0 | |
| postgres/postgres | 20.1K | C | other | |
| pingcap/tidb | 40.2K | Go | Apache-2.0 | |
| timescale/timescaledb | 21.9K | C | other | |
| cberner/redb | 4.2K | Rust | apache-2.0 | |
| snapchat/keydb | 12.5K | C++ | BSD-3-Clause | |
| cloudnative-pg/cloudnative-pg | 8.1K | Go | apache-2.0 | |
| jankotek/mapdb | 5K | Java | Apache-2.0 | |
| vitessio/vitess | 20.8K | Go | apache-2.0 |