Curated Directory of Cloud-Native Relational Databases, Sharding Gateways, and NewSQL Engines
Comprehensive guide to Horizontal Scalability, ACID Transactions, Consensus Protocols (Raft & Paxos), and Cloud-Native NewSQL Operations.
Distributed SQL databases (frequently referred to as NewSQL) combine the transactional guarantees and relational capabilities of traditional RDBMS (PostgreSQL, MySQL, SQL Server) with the horizontal scalability and fault-tolerance of NoSQL architectures.
- 🔄 Horizontal Write & Read Scaling: Scale compute and storage dynamically across nodes, availability zones, and multi-cloud geographic regions.
- 🛡️ Distributed ACID Guarantees: Native support for multi-statement, multi-shard transactions with Serializable or Snapshot Isolation without sacrificing correctness.
- 🌐 Consensus Replication: Data replicas synchronized using Raft or Paxos protocols, guaranteeing automatic failover with zero data loss (RPO=0, low RTO).
- 🔌 Wire Protocol Compatibility: Full drop-in wire and ecosystem compatibility with PostgreSQL or MySQL drivers, ORMs, and BI reporting tools.
- ⚡ Hybrid Transactional/Analytical Processing (HTAP): Single engine executing low-latency point queries alongside real-time analytical aggregation.
- 📊 Sector Overview & Market Dynamics
- ☁️ SaaS / Managed Cloud SQL Platforms
- 💻 Open-Source Distributed Database Projects
- 🤝 How to Contribute
⚠️ Architecture Trade-Offs & Disclaimer- 💖 Support & Sponsorship
- 📈 Star History
The global distributed SQL and cloud-native database market is estimated at approximately $25–30 billion in 2026, expanding at a compound annual growth rate (CAGR) exceeding 20% driven by multi-cloud resilience requirements, microservice decentralization, and mission-critical transactional volumes.
The sector demonstrates moderate concentration with a barbell distribution:
- Hyperscalers (Consolidated Core): Cloud titans—AWS Aurora, Google Cloud SQL/Spanner, and Azure SQL—capture significant market share for single-cloud enterprises demanding integrated managed operational tiers.
- Specialized NewSQL Leaders (High Innovation Moat): Independent engines (such as CockroachDB, TiDB, YugabyteDB, and Neon) command the frontier for zero-downtime geo-partitioning, vendor-agnostic deployments, copy-on-write branching, and true distributed horizontal write sharding.
The table below outlines leading enterprise cloud and SaaS platforms providing managed and distributed SQL engines. Sorted in descending order by company valuation / parent revenue scale.
The following active open-source projects power distributed SQL, horizontally scalable relational workloads, and distributed query processing. Sorted in descending order by GitHub_Stars.
-
ClickHouse
🚀 Column-oriented distributed SQL DBMS for real-time analytical reporting (Apache-2.0). Blazing-fast SQL queries over petabytes of distributed data with linear scale-out. -
DuckDB
🦆 In-process SQL OLAP database management system (MIT). High-performance analytical query processing with seamless zero-copy integration across Apache Arrow, Parquet, and distributed analytical engines. -
TiDB
⚡ Cloud-native, distributed SQL database for modern applications (Apache-2.0). MySQL protocol compatible with horizontal write scalability, strong consistency via Raft, and real-time HTAP engine. -
SurrealDB
🔮 Multi-model distributed database combining SQL, graph, and document store queries with distributed ACID transactions, real-time live queries, and granular permission access. -
CockroachDB
🪳 Cloud-native distributed SQL database architected for high availability, zero-downtime rolling upgrades, geo-partitioning, and strongly consistent distributed ACID transactions with PostgreSQL wire compatibility. -
TDengine
📈 Open-source distributed time-series database with full SQL support (AGPL-3.0). High-throughput ingestion, data caching, stream processing, and multi-node clustering for IoT and industrial big data. -
Neon
🟢 Serverless open-source alternative to AWS Aurora Postgres (Apache-2.0). Decouples compute and storage, offering instant database branching, scale-to-zero, and petabyte-scale cloud-native storage. -
Vitess
🌐 Database clustering system for horizontal scaling of MySQL (Apache-2.0). Battle-tested at YouTube, Slack, and GitHub; encapsulates shard routing, dynamic resharding, connection pooling, and failover. -
Apache ShardingSphere
🔮 Distributed SQL ecosystem providing a transparent database gateway (Apache-2.0). Adds distributed transactions, horizontal sharding, read/write splitting, and data encryption to any standard relational database. -
rqlite
💡 Lightweight, distributed relational database built on SQLite and the Raft consensus protocol (MIT). Provides effortless clustering, replication, and fault tolerance with an easy HTTP/SQL interface. -
QuestDB
⏱️ High-performance, open-source distributed SQL time-series database (Apache-2.0). Column-oriented architecture with SIMD vectorization, InfluxDB Line Protocol ingestion, and PostgreSQL wire compatibility. -
Apache Doris
🐬 High-performance, real-time distributed analytical database (Apache-2.0). Supports high-concurrency point queries, sub-second reporting, and interactive analysis with standard MySQL protocol compatibility. -
Citus
🐘 PostgreSQL extension that transforms Postgres into a distributed database (AGPL-3.0). Horizontally shards tables across multiple nodes with distributed queries, reference tables, and columnar storage. -
StarRocks
⭐ Next-generation sub-second distributed OLAP database (Apache-2.0). Features a vectorized execution engine, cost-based optimizer, real-time materialized views, and unified query acceleration over data lakes. -
YugabyteDB
🪐 High-performance distributed SQL database for mission-critical apps (Apache-2.0 core). Combines complete PostgreSQL runtime and wire compatibility with Google Spanner-inspired distributed Raft consensus and auto-sharding. -
OceanBase
🌊 Enterprise-grade distributed relational database designed for ultra-high transaction concurrency and multi-cloud resilience (MulanPubL-2.0). Native multi-tenancy, Paxos-based high availability, and HTAP capabilities. -
Apache Ignite
🔥 Distributed database, caching, and in-memory data grid platform (Apache-2.0). Delivers distributed ACID transactions, ANSI-99 SQL support, machine learning APIs, and real-time processing capabilities.
Contributions make the open-source and data community thrive! Feel free to add new distributed SQL engines or update existing information:
- 🍴 Fork this repository.
- 🌿 Create your feature branch:
git checkout -b feature/new-database - 📝 Add your entry to
README.mdfollowing the existing format (include link, license, description, and pricing/Stars_Badge). - 🚀 Commit your changes:
git commit -m "Add NewDistributedDatabase" - 📤 Push to the branch:
git push origin feature/new-database - 🎯 Open a Pull Request with a clear description of the project.
- 📌 Managed Cloud SQL vs. True Distributed SQL: Amazon Aurora, Google Cloud SQL, and Azure SQL Database decouple storage or provide read replicas, but write workloads funnel through a primary node. In contrast, TiDB, CockroachDB, and YugabyteDB are true NewSQL engines that shard writes across nodes using Raft/Paxos consensus.
- 🔌 Wire Compatibility & Migration Friction: TiDB provides low-friction drop-in MySQL compatibility. CockroachDB, YugabyteDB, and Citus offer PostgreSQL compatibility. Check your ORMs, stored procedure dependencies, and query patterns prior to migration.
- 📜 Licensing Considerations: Several engines use dual licenses or non-standard source licenses for commercial enterprise tooling (e.g. CockroachDB Software License). Verify compliance with your legal and organizational standards.
- 🛡️ Operational Complexity: Self-hosting distributed databases requires deep DBA expertise around consensus quorum, multi-AZ networking latency, backup strategies, and rolling updates.
If you find this curated ecosystem list helpful for your database engineering, architecture decisions, or research, please consider showing your support:
- ⭐ Star this repository to help others discover it!
- 🍴 Fork and contribute updates or additional engines.
- 📢 Share with your team and on social networks.
- ☕ Sponsor or buy a coffee: Support ongoing maintenance via the GitHub Sponsors Dashboard.