This article explains how TiDB, a distributed NewSQL database, combines horizontal scalability with ACID transactions and MySQL compatibility, eliminating the need for manual sharding middleware while supporting both OLTP and OLAP workloads through its HTAP architecture.
This article provides a structured decision framework for choosing databases in new projects, covering four key questions, relational and NoSQL comparisons, Xinchuang (domestic) database options, distributed NewSQL systems, a practical decision tree, typical technology stacks, and guidance on writing selection documents with POC validation.
This article explains how TiDB's NewSQL architecture eliminates manual sharding by providing horizontal scaling, ACID transactions, and MySQL compatibility through a distributed architecture with TiKV storage, PD scheduling, and TiFlash for HTAP workloads.
This article introduces NewSQL databases, compares popular products such as TiDB, CockroachDB, SingleStore, and YugaByteDB, explains HTAP architecture and storage‑compute separation, demonstrates TiDB configuration and serverless scaling, and provides concrete migration and real‑time analytics examples with code snippets.
The article objectively compares middleware‑based sharding with NewSQL distributed databases, examining distributed transactions, CAP constraints, HA, scaling, storage engines, maturity, and ecosystem, and offers a decision framework for choosing the appropriate architecture based on concrete requirements.
The article reviews the rise and decline of traditional database sharding, explains its technical pitfalls such as wrong shard keys, cross‑database joins, and distributed transactions, compares it with emerging NewSQL solutions like TiDB, OceanBase and PolarDB‑X, and offers practical criteria for choosing the right architecture.
This article objectively compares middleware‑based sharding solutions with native NewSQL distributed databases, examining their architectural differences, transaction handling, high‑availability, scaling, SQL support, storage engines, and maturity to help engineers decide which approach best fits their workload.
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 details the TiDB upgrade journey from version 5.3.3 to 7.5.x, covering architecture, new v7 features, migration strategies, encountered problems with full‑table scans and inaccurate aggregation plans, the solutions applied, and the measurable performance and stability gains achieved after the upgrade.
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 objectively compares middleware‑based sharding with NewSQL distributed databases, examining their architectures, transaction support, CAP implications, high‑availability, scaling, storage engines, and ecosystem maturity to help readers decide which solution best fits their workload.
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 objectively compares middleware‑based sharding with NewSQL distributed databases, examining architecture, distributed transactions, performance, high availability, scaling, SQL support, storage engines, and ecosystem maturity to help architects decide which solution fits their specific workload and operational constraints.
This article objectively compares middleware‑based sharding with NewSQL distributed databases, examining their architectural differences, transaction models, high‑availability mechanisms, scaling, SQL support, storage engines, and maturity to help practitioners decide which approach best fits their workload and operational constraints.
This article objectively compares NewSQL distributed databases with traditional middleware‑based sharding solutions, examining their architectures, distributed transaction handling, high‑availability, scaling, storage engines, and ecosystem maturity, and provides guidance on selecting the appropriate approach based on consistency, growth, operational capacity, and performance requirements.
The article objectively compares NewSQL distributed databases with middleware‑plus‑sharding solutions, covering architectural differences, distributed transaction handling, high‑availability, scaling, SQL support, storage engines, maturity, and provides a decision‑making checklist to help engineers select the most suitable approach for their workloads.
This article objectively compares NewSQL databases with middleware‑based sharding, dissecting their core architectures, distributed transaction handling, high‑availability designs, scaling mechanisms, SQL support, storage engines, and maturity to help engineers decide the most suitable solution for their workloads.
This article objectively compares NewSQL distributed databases with traditional middleware‑based sharding solutions, examining their architectures, distributed transaction support, high availability, scaling, SQL capabilities, and maturity to help readers decide which approach best fits their workload and operational constraints.
An in‑depth comparison of NewSQL databases and middleware‑based sharding reveals each approach’s architectural strengths, distributed transaction handling, scalability, HA mechanisms, storage engine design, and ecosystem maturity, guiding readers on when to adopt NewSQL versus traditional sharding solutions.
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.
Baidu’s Canghai Storage unifies metadata, hierarchical namespace, and data layers into a Meta‑Aware, three‑generation architecture that scales to trillions of metadata items and zettabyte‑scale data, using a distributed transactional KV store, single‑machine‑distributed namespace, and online erasure‑coding micro‑services to deliver high performance, low cost, and seamless scalability.
This article objectively compares NewSQL distributed databases with traditional middleware‑based sharding, examining their architectural advantages, distributed transaction handling, high‑availability mechanisms, scaling and sharding strategies, storage engine differences, ecosystem maturity, and provides guidance on selecting the appropriate solution for various workloads.
This article objectively compares NewSQL distributed databases with traditional middleware‑based sharding solutions, examining their architectural differences, transaction support, scalability, HA, storage engines, and ecosystem maturity, to help readers decide which approach best fits their performance, consistency, and operational needs.
This article objectively compares NewSQL databases with middleware‑based sharding solutions, examining architecture, distributed transactions, CAP constraints, high availability, scaling, SQL support, storage engines, and maturity to help readers choose the right approach for their workloads.
This article surveys two decades of database system architecture innovations—including columnar stores, cloud databases, data lakes, NewSQL, hardware accelerators, and blockchain databases—highlighting their motivations, trade‑offs, and the shifting landscape that shapes modern DBMS design.
This article objectively compares NewSQL distributed databases with traditional middleware‑based sharding solutions, examining their architectures, transaction models, scalability, high‑availability mechanisms, storage engines, maturity, and offering a decision framework to help engineers choose the most suitable approach for their workloads.
This article explains what NewSQL databases are, outlines their core characteristics, reviews major products such as Spanner, CockroachDB, TiDB, OceanBase and TDSQL, and discusses typical use cases ranging from financial services to HTAP workloads.
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.
This article objectively compares NewSQL databases with middleware‑based sharding solutions, examining their architectures, distributed transaction handling, scalability, high‑availability mechanisms, storage engines, and suitability for various workloads, and provides guidance on selecting the appropriate approach based on specific system requirements.
This article objectively compares NewSQL distributed databases with traditional middleware‑based sharding solutions, examining their architectures, distributed transaction support, high availability, scaling, storage engines, SQL capabilities, maturity, and suitability for various workloads, to help architects decide which approach best fits their needs.
This article objectively compares NewSQL databases with middleware‑based sharding solutions, examining their architectural differences, transaction handling, scalability, high‑availability mechanisms, storage engines, and maturity to help readers decide which approach best fits their specific workload and business requirements.
This article objectively compares NewSQL databases and middleware‑plus‑sharding architectures, examining their core principles, distributed transaction handling, high‑availability mechanisms, scaling and sharding strategies, SQL support, storage engines, and maturity to help engineers decide which solution fits their workload.
This article objectively compares middleware‑based sharding with modern NewSQL distributed databases, examining their architectural differences, performance, transaction support, scalability, high‑availability, and operational considerations, to help practitioners decide which approach best fits their workload and organizational constraints.
The article objectively compares NewSQL distributed databases with traditional middleware‑based sharding solutions, examining their architectural differences, distributed transaction support, performance, scalability, high‑availability mechanisms, storage engines, and practical suitability for various 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 explains what distributed databases are, outlines their four key characteristics—high performance, scalability, high availability, and data consistency—and reviews five prominent systems (OceanBase, TDSQL, Google Spanner, CockroachDB, and TiDB) that illustrate these concepts in real‑world applications.
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.
The 2023 first‑half newsletter compiles a comprehensive overview of the database sector, highlighting the surge of domestic vendors, key technological breakthroughs such as HTAP and serverless, and detailed version updates across RDBMS, NewSQL, graph, time‑series, big‑data, and cloud databases, offering valuable insights for practitioners and decision‑makers.
This article traces the history of database development from early file systems to relational models, outlines major database categories such as hierarchical, relational, NoSQL, NewSQL, and columnar stores, and explores practical data structure designs like chain tables, bitwise operations, and circular queues for modern software engineering.
TiDB is a distributed NewSQL database that combines horizontal scalability, ACID transactions, full MySQL compatibility, and real‑time HTAP capabilities, offering a unified solution for OLTP, OLAP, and hybrid workloads while addressing the limitations of traditional SQL and NoSQL systems.
This article explains the evolution from traditional SQL to NewSQL, outlines the limitations of classic relational and NoSQL databases, and details TiDB's architecture, core features, high‑availability design, compatibility with MySQL, and real‑world use cases for both OLTP and OLAP workloads.
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 walks through turning a basic personal‑blog architecture—single server, MySQL, and Node.js—into a high‑concurrency system by adding Redis caching, Nginx load balancing, horizontal scaling, read‑write splitting, sharding, NewSQL databases, and message‑queue techniques.
This article explains how to transform a simple personal‑blog backend into a high‑performance, horizontally scalable system by introducing caching with Redis, load balancing with Nginx/LVS, read/write separation, database sharding, and modern NewSQL solutions such as TiDB, while also discussing related challenges like cache consistency and data migration.
This article explains how to choose storage options, design sharding keys, apply partitioning strategies, modify business code, handle historical data migration, and plan future scaling for large‑scale e‑commerce systems using MySQL, NoSQL, and NewSQL solutions.
This article explains the concept of consistency in distributed transactions, compares strong and weak consistency, relates it to the CAP theorem, and explores theoretical and practical approaches—including XA, NewSQL, and MVCC—to achieve stronger consistency across databases and micro‑services.
This article traces the evolution of database systems—from the first network and hierarchical models through relational databases, NoSQL sharding, and finally modern distributed SQL—explaining why distributed databases emerged, how they handle data distribution, consistency, SQL-to‑KV mapping, and transaction challenges.
Tongcheng Yilong’s BaikalDB deployment combines high‑availability multi‑Raft HA, HTAP support, and share‑nothing scalability to deliver over 72K TPS OLTP and ten‑fold faster OLAP queries while cutting operational costs up to a hundredfold through dual‑center, columnar storage and cloud‑native elasticity.
This article explains the fundamentals of transparent sharding middleware in NewSQL systems, covering data partitioning strategies, read/write separation, the complete SQL processing pipeline, protocol adaptation for MySQL/PostgreSQL, distributed transaction models such as XA, Saga and TCC, and essential database governance and online scaling techniques.
This article details how Zhihu’s Moneta service, handling over a trillion rows of user‑read data, migrated from MySQL sharding and MHA to the open‑source NewSQL database TiDB, achieving millisecond‑level query latency, high write throughput, and improved scalability through a layered architecture and TiDB’s advanced features.
This article objectively compares NewSQL distributed databases with traditional middleware‑plus‑sharding solutions, examining architecture, distributed transactions, CAP constraints, high‑availability, scaling, storage engines, maturity, and practical adoption scenarios to help readers decide which approach best fits their needs.
This article objectively compares NewSQL distributed databases with traditional middleware‑plus‑sharding solutions, examining their architectural differences, distributed transaction handling, high‑availability mechanisms, scaling and sharding strategies, SQL support, storage engines, and maturity to help practitioners decide which approach best fits their workload and operational constraints.
This article objectively compares NewSQL distributed databases with middleware‑based sharding solutions, examining their architectural differences, distributed transaction handling, high‑availability mechanisms, scaling and sharding strategies, SQL support, storage engines, and overall maturity to help readers decide which approach best fits their workload.
This article details how Zhihu tackled the massive data and latency challenges of its Moneta service by migrating from MySQL sharding and MHA to the distributed NewSQL database TiDB, describing the new three‑tier architecture, performance gains, migration tactics, and expectations for TiDB 3.0.
This article describes how Zhihu’s Moneta application migrated billions of rows of user‑read data to the open‑source MySQL‑compatible NewSQL database TiDB, detailing the architectural redesign, performance improvements, migration challenges, and future expectations for TiDB 3.0.
This article details Zhihu's Moneta service handling over a trillion rows, the scalability challenges it faced, the evaluation of MySQL sharding and MHA, and how adopting the open‑source HTAP database TiDB enabled millisecond‑level query latency, high availability, and easy horizontal expansion.
TiDB is a distributed NewSQL database that combines MySQL compatibility with a stateless SQL layer, a PD metadata manager, and a transactional key‑value store, offering automatic scaling, multi‑data‑center Raft replication, global secondary indexes, Percolator‑style 2PC, HTAP via TiFlash, and a rich ecosystem of migration, backup, CDC, and monitoring tools, as demonstrated by its large‑scale deployment at DeWu.
This article examines the evolution of database architectures, introduces the hot‑data and cold‑data concepts for a weather‑data service, and details a practical implementation using MySQL, TiDB, and PolarDB with synchronization, expiration procedures, and suggestions for future improvements.
This article objectively compares NewSQL databases with middleware‑based sharding approaches, examining their architectural differences, transaction models, CAP implications, high‑availability designs, scaling mechanisms, storage engines, maturity, and provides a decision guide to help engineers choose the right solution for their workloads.
This article objectively compares traditional sharding‑plus‑middleware architectures with modern NewSQL distributed databases, examining their design principles, distributed transaction handling, high‑availability mechanisms, scaling and sharding strategies, SQL support, storage engines, and overall maturity to help practitioners choose the most suitable solution for their workloads.
This article objectively compares NewSQL databases with middleware‑based sharding solutions, examining architecture, distributed transactions, CAP constraints, performance, high availability, scaling, SQL support, storage engines, maturity, and provides practical guidance for choosing the right approach.
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.
The 2019 dbaplus Newsletter compiles a detailed overview of major RDBMS, NoSQL, NewSQL, big‑data, Chinese and cloud database releases, highlighting key features, performance improvements, security enhancements, and future road‑maps for each product.
This article outlines the three generations of databases—SQL, NoSQL, and NewSQL—explaining the limitations of traditional relational systems, the scalability and consistency trade‑offs of NoSQL, and how NewSQL combines distributed architecture with ACID guarantees, while also listing major NewSQL projects.
The article details the three‑stage evolution of 58.com’s distributed key‑value storage system WTable, covering its initial architecture, performance and operational optimizations, and the introduction of NewSQL‑style strong consistency and Raft‑based replication to improve scalability and reliability.
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.
The article traces how each mobile generation—from 1G’s early relational databases to 2G’s open‑source RDBMS, 3G’s scalable NoSQL, 4G’s NewSQL hybrids, and the emerging 5G era demanding ultra‑low latency, cloud‑native, AI‑driven real‑time analytics—shapes database architecture and future trends.
This article objectively compares NewSQL distributed databases with middleware‑based sharding solutions, examining their architectures, distributed transaction handling, scalability, performance, high‑availability, and operational considerations, and provides guidance on selecting the appropriate approach based on workload, consistency, and organizational constraints.
This article explores the resurgence of SQL, tracing its historical roots, the rise and limitations of NoSQL, and how modern cloud and NewSQL solutions are re‑establishing SQL as the universal interface for data storage, processing, and analysis.
The article explains the concept of transparent scalable NewSQL databases, discusses the historical challenges of scaling relational systems, and details the design and implementation techniques—such as dynamic sharding, distributed transactions, consensus algorithms, distributed SQL, and CB‑SQL’s specific mechanisms like HLC, SSI isolation, Multi‑Raft, and automatic load balancing—to achieve elasticity, high availability, and seamless scalability.
The article explores TiDB’s evolution philosophy, detailing its core beliefs, early user stories, and the three‑step "Make it work, make it right, make it fast" approach, while covering technical choices such as cloud‑first design, hardware‑agnosticism, formal verification, massive testing, performance tuning, and cost‑effective scaling.
Fusion, Didi’s home‑grown C++ NoSQL database built on RocksDB, powers over 400 services and 1.5 PB of data, then evolved into the NewSQL layer dise with schema, secondary indexes, transactions and MySQL‑compatible binlog, and now guides a next‑gen distributed database project targeting true elastic scaling, distributed transactions and full SQL compatibility.
This article details Didi's evolution from a self‑built NoSQL system called Fusion to a NewSQL solution and outlines the challenges, architectural highlights, data migration mechanisms, and future distributed database design, providing concrete metrics, diagrams, and practical lessons learned.
This article explains how to map relational table rows and various indexes—including primary key, integer, float, string, and composite indexes—into RocksDB key‑value pairs using custom serialization, big‑endian ordering, and encoding functions to enable efficient point, range, and multi‑field queries.
The Beijing technical exchange detailed Tencent Cloud CynosDB’s compute-storage separation architecture, explaining how CynosStore’s block and file-system layers asynchronously persist write-ahead logs via Raft, provide multi-transaction atomicity, continuous snapshots, and rapid recovery, while benchmarks demonstrate high log-throughput and the Q&A covered tenancy, failover, and scaling.
The January 2019 DB-Engines newsletter compiles the newest releases, feature highlights, and performance improvements across RDBMS, NoSQL, NewSQL, time‑series, big‑data, domestic, and cloud database families, while also explaining the ranking methodology and providing download links for the full issue.
Chubao Database (CBDB) is a second-generation elastic, multi-model database service that supports KV, document, graph, and SQL models via multiple protocols, simplifying stacks, reducing costs, and providing horizontal scalability, high availability, strong consistency, and distributed transactions.
CynosDB is Tencent Cloud’s high‑performance, highly‑available NewSQL distributed database that uses a shared‑storage architecture with primary and replica instances, log‑structured storage, RDMA/SPDK transmission, Raft consensus, SSI MVCC, two‑phase locking, and state‑machine replication to provide elastic scaling, fast recovery, and cost‑effective enterprise data management.
This article presents a chronological overview of Optimistic Concurrency Control (OCC), covering its early theoretical foundations, key research papers, prototype implementations such as MVCC+OCC+2PC and Hekaton, and its adoption in modern distributed NewSQL databases like Megastore, F1, and MaaT, highlighting both advantages and challenges.
This article examines the evolution and classification of distributed databases for OLAP workloads, comparing traditional RDBMS, MPP solutions such as Teradata and Greenplum, Hadoop‑based ecosystems, and newer architectures like ClickHouse and Palo, while highlighting their architectural traits, strengths, and limitations.
The article details Minsheng Bank’s shift to distributed architecture, outlining regulatory drivers, business requirements, the adoption of sharding, cross‑center high‑availability, and new‑type distributed databases, and showcases performance results of SequoiaDB 3.0 across multiple high‑throughput banking scenarios.
This article examines the core technologies behind NewSQL databases for OLTP workloads, contrasting them with NoSQL and traditional relational systems by exploring storage engines such as B‑Tree and LSM‑Tree, sharding strategies, replication models, and distributed transaction mechanisms like two‑phase commit.
The March 2018 DBAplus Newsletter compiles the latest releases across RDBMS, NoSQL, NewSQL, time‑series and big‑data ecosystems, highlighting new features, performance improvements, compatibility updates and key technical links for Oracle, MySQL, MariaDB, SQL Server, DB2, PostgreSQL, TiDB, CockroachDB, InfluxDB, Hadoop and several Chinese‑made databases.
Facing billions of rows spread across 1024 tables in 64 databases, a Chinese gaming platform replaced its custom sharding framework with TiDB, achieving real‑time OLTP consistency, elastic scaling, robust backup, high availability, and lower migration costs while preserving MySQL compatibility.
This article traces the evolution of database systems—from early navigational models and Codd's relational theory through the rise of NoSQL and sharding, to the resurgence of NewSQL and the emerging HTAP paradigm—highlighting technical motivations, design trade‑offs, and future directions.
PingCAP co‑founder and CEO Liu Qi discusses the motivation behind creating TiDB, its evolution into a HTAP NewSQL database, key development priorities such as SQL enhancements, storage engine innovation, cloud‑native integration, and shares insights on open‑source project management and future database trends.
This article interprets the 2017 SIGMOD paper on Amazon Aurora, explaining its cloud‑native architecture, key advantages such as self‑healing storage and reduced network I/O, the challenges it introduces, a comparison with traditional databases and TiDB, and insights into deployment, replication, and recovery mechanisms.
The two‑day Tongcheng Technology Conference in Suzhou featured six technical sessions covering serverless architecture, microservices with Go, Facebook‑style development tools, NewSQL database practices, hybrid cloud management at Sina Weibo, and high‑performance ticket search systems, offering practical insights for backend engineers.
The October 2017 DBAplus Newsletter summarizes the newest releases across RDBMS, NoSQL, NewSQL, time‑series, big‑data and domestic databases, highlighting key features, performance improvements, and ecosystem updates while providing links to official documentation and source repositories.