Oceanbase

OceanBase is a distributed SQL database designed for high availability and strong consistency across multiple nodes and regions. It functions as a hybrid transactional and analytical processing engine, allowing real-time analytics and transactions to execute on a single data copy. The system also serves as a vector database engine for indexing and querying vector data to power semantic search and recommendation systems.

The platform features native compatibility layers for MySQL and Oracle, enabling the migration of legacy workloads without rewriting SQL code. It utilizes a Paxos-based distributed store for synchronous replication and implements a multi-tenant architecture that isolates CPU, memory, and I/O resources for different tenants within a single cluster.

The system covers a broad range of capabilities, including horizontal storage scaling, distributed transaction management, and hybrid row-columnar storage. It provides tools for cluster orchestration, automated load balancing via log-stream migration, and disaster resilience through multi-zone replication and automated failover.

Deployment and management are supported through a Kubernetes operator and a web monitoring dashboard.

Features

Distributed SQL Databases - Functions as a relational database engine designed to scale horizontally while maintaining transactional consistency.
Hybrid Transactional Analytical Processing Systems - Functions as a hybrid transactional and analytical processing engine, allowing real-time analytics and transactions on a single data copy.
Hybrid Storage Formats - Optimizes for both transactions and analytics by storing data in both row and column formats within the same system.
Cross-Zone Data Distribution - Replicates data across multiple logical zones using a consensus protocol to ensure high availability.
Database Compatibility Layers - Provides native compatibility layers for MySQL and Oracle to migrate legacy workloads without rewriting SQL code.
Strongly Consistent Data Stores - Maintains strong consistency across distributed replicas using a Paxos-based leader-follower replication model.
Disaster Recovery Solutions - Ensures business continuity via synchronous replication and automated failover across geographically distributed infrastructure.
Distributed Consensus Protocols - Uses the Paxos consensus protocol to maintain strong data consistency across distributed replicas.
Distributed Consensus Stores - Uses a Paxos-based distributed store for synchronous replication and high availability across data zones.
Distributed Transaction Processing - Maintains ACID consistency across a distributed SQL environment to ensure data integrity for critical workloads.
Horizontal Database Scaling - Expands a single cluster across thousands of nodes to manage petabytes of data and trillions of records.
Horizontal Scaling - Increases read and write capacity by automatically balancing and routing data across new nodes.
HTAP Databases - A hybrid system that executes real-time analytics and transactions on a single data copy.
Multi-Tenant Data Management - Provides administrative interfaces for creating tenants, managing resource units and isolating data.
Multi-Tenant Resource Isolation - Implements a multi-tenant architecture that isolates CPU, memory, and I/O resources for different tenants within a single cluster.
MySQL Compatibility - Supports MySQL compatibility layers to migrate legacy workloads without extensive code rewrites.
Real-Time Analytics - Executes complex reporting and live dashboards directly on transactional data with low latency.
Vector Databases - Provides a storage engine capable of indexing and querying high-dimensional vector embeddings for semantic search.
Vector Search - Indexes and queries high-dimensional vector data to enable semantic search and recommendation systems.
Multi-Region Replication - Replicates data across different physical zones in real-time to ensure zero data loss during regional failures.
High Availability Services - Maintains continuous service uptime using automated failover and zero data loss across racks and regions.
Multi-Tenant Isolation - Separates CPU, memory, and I/O resources for each tenant using a native multitenancy architecture.
Compatibility Layers - Provides compatibility layers for Oracle and MySQL dialects to allow legacy applications to run without SQL rewrites.
Kubernetes Operators - Provides a dedicated Kubernetes operator to automate the provisioning and management of database clusters.
Standby Management - Supports creating standby tenants, restoring standbys from backups, and executing primary-standby switchovers.
Columnar Storage Engines - Lowers costs and resource usage through a hybrid row-columnar storage engine.
Cluster Request Routing - Implements mechanisms for directing SQL requests to specific nodes based on data distribution across the cluster.
Data Compression Algorithms - Reduces storage footprint and accelerates queries using dictionary, run-length, and differential compression.
Replica Recovery - Performs single-node or cluster-wide recovery and automated re-synchronization of data to replacement nodes.
Query Routing - Automatically resolves data distribution and shard locations to route queries to the appropriate server.
Traffic Scaling Strategies - Implements distributed architecture to maintain predictable performance and data consistency during traffic surges.
Hybrid Search - Combines vector similarity with structured metadata and full-text lookups in a single request.
Hybrid Vector-Keyword Indexing - Combines structured data with vector embeddings in a single storage engine to enable semantic search.
Log-Stream Balancing - Scales capacity and redistributes load by splitting and migrating data log streams between cluster nodes.
Table-Level Storage Formats - Allows defining row, column, or hybrid storage formats at the table level to apply schema changes without downtime.
Multi-Cloud Deployments - Distributes data across different regions and cloud providers to minimize latency and maintain data sovereignty.
Database Cluster Orchestration - Enables bootstrapping clusters, adjusting topology, scaling nodes, and modifying system parameters to maintain cluster health.
High Availability Systems - Implements architectural patterns to ensure continuous service availability and fault tolerance across distributed nodes.
Data - Automatically rebalances data and service loads by splitting, merging, and migrating log streams during scaling.
Database Access Controls - Provides end-to-end encryption and granular access controls to protect database assets and meet regulatory requirements.
Database Dialect Migration - Provides compatibility layers for Oracle and MySQL to transition existing database applications without extensive code rewrites.
Database Management Systems - Distributed relational database built on the Paxos protocol.

pingcap/tidb

40,166View on GitHub

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

apache/pinot

6,098View on GitHub

Pinot is a distributed, columnar analytical database designed for high-concurrency, low-latency query processing. It functions as a real-time OLAP datastore, enabling interactive, user-facing analytics by ingesting and querying massive datasets from both streaming and batch sources. The system architecture relies on a centralized controller for cluster coordination and a distributed segment-based storage model to ensure horizontal scalability. The platform distinguishes itself through a hybrid ingestion pipeline that unifies real-time event streams and historical batch data into a single quer

alibaba/AliSQL

5,706View on GitHub

AliSQL is a fork of MySQL by Alibaba that extends the relational database management system with enhancements for high performance, scalability, and enterprise-grade availability. It retains the core MySQL identity as a SQL-based database for storing, organizing, and retrieving structured data, while adding optimizations for large-scale transactional and analytical workloads. The project differentiates itself through a set of Alibaba-specific improvements, including a columnar engine for accelerating analytical queries directly on MySQL tables, and a distributed, shared-nothing NDB Cluster en

citusdata/citus

12,562View on GitHub

Citus is a PostgreSQL extension that transforms a standard database into a distributed system. It functions as a sharding framework and distributed SQL engine, enabling horizontal scaling by partitioning tables across a cluster of nodes. By utilizing a coordinator-worker topology, the system manages metadata and routes queries to the appropriate nodes, allowing for parallel execution of complex operations across distributed data shards. The platform distinguishes itself through its specialized support for multi-tenant architectures and real-time analytical processing. It enables tenant-based

oceanbaseoceanbase

Features