Dolt is an open‑source, MySQL‑compatible database that embeds Git’s version‑control model, letting you commit, branch, merge and audit table data just like source code, with simple installation, CLI commands, SQL stored procedures, GitHub remote support, and CI integration.
This article analyzes TiDB as a distributed NewSQL database, explaining the evolution from traditional SQL to NoSQL and NewSQL, detailing TiDB's core components, elastic scaling, ACID transactions, HTAP capabilities, high‑availability design, compatibility with MySQL, real‑world use cases, and its limitations compared to conventional databases.
This article explains NewSQL concepts, compares traditional SQL, NoSQL and NewSQL, and provides an in‑depth overview of TiDB’s architecture, high‑availability design, HTAP capabilities, MySQL compatibility, configuration differences, and real‑world application scenarios.
TiDB is a distributed NewSQL database that combines horizontal elasticity, strong ACID transactions, MySQL compatibility, and built‑in HTAP capabilities, making it suitable for high‑availability, large‑scale OLTP and OLAP workloads while addressing the limitations of traditional relational and NoSQL systems.
TiDB is a cloud‑native NewSQL distributed database that combines horizontal elastic scaling, ACID transactions, and full MySQL compatibility, offering a unified solution for both OLTP and OLAP workloads while delivering high availability and strong consistency across large‑scale applications.
This article provides a comprehensive introduction to TiDB, a NewSQL distributed database, covering its origins, core components, high‑availability design, NewSQL characteristics, differences from traditional SQL and NoSQL, compatibility with MySQL, configuration nuances, and typical use cases such as HTAP and cloud‑native deployments.
This article provides a comprehensive introduction to TiDB, a distributed NewSQL database that combines OLTP and OLAP capabilities, explains NewSQL concepts, compares traditional SQL, NoSQL and NewSQL, details TiDB's architecture and core components, highlights its high‑availability and scalability features, and outlines compatibility differences and practical use cases.
This article provides a comprehensive overview of TiDB, a cloud‑native NewSQL database that combines the scalability of NoSQL with the strong consistency of traditional relational databases, detailing its architecture, high‑availability design, HTAP capabilities, MySQL compatibility, and practical application scenarios.
TiDB, an open‑source NewSQL distributed database, combines the strong consistency and ACID guarantees of traditional relational databases with the scalability of NoSQL, offering cloud‑native architecture, HTAP capabilities, high availability, and seamless MySQL compatibility, while highlighting NewSQL concepts, design trade‑offs, and migration scenarios.
This article provides a comprehensive overview of TiDB, an open‑source distributed NewSQL database, covering its origins, architecture components, high‑availability design, HTAP capabilities, MySQL compatibility, differences from traditional SQL and NoSQL, and practical deployment scenarios.
This article provides a comprehensive technical overview of NewSQL concepts and TiDB, covering its origins, core features, distributed architecture, high‑availability design, MySQL compatibility, unsupported MySQL functionalities, configuration defaults, and real‑world application scenarios for both OLTP and OLAP workloads.
TiDB is an open‑source NewSQL database that combines horizontal scalability, strong ACID guarantees, MySQL compatibility, and cloud‑native design to support both OLTP and OLAP workloads, offering high availability and real‑time HTAP capabilities for large‑scale applications.
This article explains the evolution from traditional SQL and NoSQL to NewSQL, outlines the limitations of each, and provides an in‑depth look at TiDB—a cloud‑native, distributed NewSQL database—covering its architecture, core features, high‑availability design, compatibility with MySQL, and typical use cases.
This article provides a comprehensive introduction to TiDB, a distributed NewSQL database, covering the evolution from traditional SQL to NoSQL, NewSQL characteristics, TiDB’s origin, core components, high‑availability design, cloud‑native architecture, compatibility with MySQL, unsupported features, and typical use cases such as sharding, data warehousing, and HTAP workloads.
This article explains the evolution from traditional SQL to NewSQL, outlines the shortcomings of classic relational databases and NoSQL, and details TiDB’s architecture, core features, high‑availability design, and practical use cases as a cloud‑native, MySQL‑compatible HTAP solution.
This article provides a comprehensive overview of TiDB, a NewSQL distributed database, covering its origins, core features such as horizontal scaling, ACID transactions, HTAP support, cloud‑native design, MySQL compatibility, architectural components, high‑availability mechanisms, application scenarios, and differences from traditional MySQL implementations.
This article demonstrates how to deploy OceanBase 4.X in a minimal single‑node configuration, explains the key resource parameters, provides the necessary YAML configuration and command‑line steps to start the server, create a MySQL‑compatible tenant, and verify resource usage and basic database operations.
The OceanBase 4.0 core technology presentation recounts twelve years of evolution from the early 0.1 version to a single-node distributed integrated database, highlighting breakthroughs such as sub-8-second RTO, RPO = 0, Paxos three-replica high availability, and competitive performance in TPC-C and TPC-H benchmarks.
PolarDB‑X evolved from Alibaba’s internal sharding middleware TDDL to the DRDS cloud service and finally to a fully distributed MySQL‑compatible database, introducing a full SQL optimizer, MPP engine, global secondary indexes, strong‑consistent distributed transactions via TSO + 2PC, and full binlog compatibility.
This article explains the role of distributed architecture for high‑performance internet systems, introduces GreatSQL as a native distributed relational database, compares it with MySQL, and provides step‑by‑step Docker‑Compose instructions to set up, start, and verify a three‑node MGR cluster, plus integration with the PIG microservice platform.
TiDB, an open‑source distributed relational database, separates compute and storage, offers MySQL compatibility, supports both OLTP and OLAP workloads, and provides HTAP capabilities, with real‑world use cases ranging from MySQL sharding to full replacement, data warehousing, and serving as a modular component.
TiDB is an open‑source, cloud‑native distributed relational database that combines OLTP and OLAP capabilities, offers horizontal elasticity, strong ACID transactions, MySQL compatibility, and is suited for high‑availability, large‑scale, real‑time analytics scenarios across various industries.
This article explains how TiDB, a MySQL‑compatible distributed NewSQL database, solves large‑table performance issues with horizontal scaling, describes its core components, deployment guidelines, key advantages, and practical tips such as avoiding auto‑increment IDs, handling hotspots, version quirks, backup strategies, and monitoring with Grafana.
This article introduces TiDB, an open‑source distributed HTAP database compatible with MySQL, explains its architecture—including TiDB Server, PD, TiKV, and TiSpark—covers deployment requirements, highlights key advantages such as elastic scaling, fault‑tolerance, strong consistency, and provides practical tips and common pitfalls for production use.
Zhihu's Moneta service stores over a trillion rows of user‑read posts and, facing massive write throughput and strict sub‑90 ms query latency requirements, migrated to the open‑source HTAP database TiDB, achieving horizontal scalability, high availability, and dramatically improved performance.
Fusion-NewSQL is Didi’s internally‑developed NewSQL system built atop the Fusion distributed KV store, offering MySQL compatibility, high throughput, low latency, flexible schema changes, secondary indexes, and integration with ElasticSearch and Hive, with detailed architecture, data flow, and future roadmap.
Fusion‑NewSQL is a NewSQL layer built atop Didi’s distributed KV store Fusion, translating MySQL queries into Redis‑style hashmaps, asynchronously maintaining secondary indexes, supporting fast Hive‑to‑Fusion loads and Elasticsearch integration, thereby delivering over 2 million QPS, 600 TB storage and flexible schema evolution for dozens of services.
This article introduces Apache Doris, a massively parallel processing (MPP) distributed database, covering its background, core architecture, key technologies such as reliability, maintenance, MySQL compatibility, materialized views, and real‑world applications at Baidu and beyond.
Facing rapid traffic growth and MySQL limitations, Tongcheng migrated its ticketing order database to a sharded MySQL cluster combined with TiDB, achieving transparent sharding, real‑time synchronization, high‑availability monitoring, and seamless handling of billions of rows and peak QPS over 10,000.
This article details how Tongcheng Network migrated massive ticketing and flight‑booking workloads to TiDB, combining sharding and a distributed SQL database to handle terabytes of data, real‑time monitoring, and high QPS traffic while simplifying operations and reducing costs.
The article outlines UDDB’s roadmap from a MySQL‑compatible middleware to a full‑featured distributed database, detailing its three‑stage evolution, system architecture, SQL parsing and routing design, and innovative techniques that enable read‑write separation, vertical sharding, and future horizontal scaling.
TiDB’s founder Huang Dongxu recounts the journey of building a MySQL‑compatible, distributed database—detailing early challenges, architectural decisions, the extensive testing, the adoption of Go, Rust, Raft, RocksDB, and the emphasis on metrics, cloud‑native design, and open‑source community collaboration.
This article explains how PhxSQL prioritizes strong linearizable consistency, high availability, serializable isolation, and full MySQL compatibility, and why it deliberately forgoes features such as multi‑write, sharding, and strict serializable isolation due to the high cost of distributed transactions and protocol complexity.
