Beads is a command‑line tool that turns Git into a distributed database, giving AI coding agents persistent, collaborative, and dependency‑aware task tracking, with features like context offloading, native dependency graphs, dual‑storage write barriers, adaptive hash IDs, and performance‑optimised blocked‑issue caching.
This article explains TiDB's distributed, financial‑grade high‑availability architecture, covering single‑cluster same‑zone multi‑datacenter deployment, cross‑cluster DTS synchronization, underlying Raft and label mechanisms, configuration examples, performance trade‑offs, and real‑world monitoring results on the HULK cloud platform.
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.
A customer observed a SQL statement that runs twice as fast on Oracle as on OceanBase, prompting a detailed analysis of execution plans, leader distribution, and distributed query behavior, followed by practical hint and table‑group optimizations that reduce the runtime from several seconds to sub‑second levels.
PolarDB‑X version 2.4.2 introduces a Java‑based proxy, multi‑language client drivers, enhanced HA switching, MySQL‑compatible replication, performance testing results, and the open‑source MCP server for AI integration, providing a comprehensive overview of the latest distributed database capabilities.
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 deeply analyzes ShardingSphere-JDBC 5.3.0 source code, explaining its JDBC‑compatible sharding design, modular architecture, adapter pattern implementation, SQL parsing and routing, distributed transaction support, elastic scaling, performance optimizations, and extensibility via SPI.
This paper presents the design, implementation, and experimental evaluation of OceanBase's unitization architecture for large‑scale online map services, demonstrating superior disaster‑recovery, high‑throughput OLTP/OLAP performance, and storage efficiency compared with competing distributed databases.
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.
Redis Cluster provides a scalable, fault‑tolerant distributed Redis solution, explaining why it’s needed, its architecture, virtual slot partitioning, data distribution methods, limitations, smart client optimization, and automatic failover mechanisms, while highlighting key operational considerations for high‑performance deployments.
This article introduces Easysearch, a lightweight, secure, Elasticsearch‑compatible search database, outlines its core features and applicable scenarios, and provides a step‑by‑step CentOS 7 deployment guide together with practical verification commands and future development considerations.
The article explains how Databricks’ scaling challenges with PostgreSQL inspired the creation of DBOS, a database‑oriented operating system that places the OS beneath a distributed transactional database to simplify task scheduling, state management, and cloud‑native workloads.
vivo migrated five 20‑TB MySQL clusters to OceanBase using OCP, oblogproxy, and OMS, eliminating sharding costs, achieving over 70% storage savings, improving consistency and performance, and leveraging native distributed architecture, tenant isolation, and strong compression to support scalable, reliable operations.
This article walks through building a database storage engine from a simple shell script to a full distributed key‑value system, covering in‑memory indexing, SSTable creation, LSM‑Tree architecture with compaction, replication strategies, and sharding techniques for scaling across multiple machines.
OceanBase employs a shared‑nothing distributed cluster design where each node runs its own SQL, storage, and transaction engines, evolving through versions 0.5 to 4.0 to improve scalability, high availability, and low latency, while supporting multi‑tenant deployments and TPC‑C benchmark success.
The article introduces PolarDB‑X version 2.4.1, detailing its enterprise‑grade operational enhancements such as cloud backup set restore, native online DDL with OMC, physical file‑based scaling, flexible data TTL, the overall architecture, and various deployment options for multi‑cloud environments.
This article explains TiDB’s distributed relational database architecture, compares Kubernetes‑based and physical‑machine deployments, and describes Zhihu’s platform‑driven approach—including TiDB Operator, TiUP, self‑service tooling, monitoring, backup, security, and FinOps—to enable efficient database management for both developers and DBAs.
This report examines how Yum China and PingCAP’s joint innovation lab applies TiDB’s distributed database capabilities—such as elastic scaling, real‑time analytics, HTAP architecture, and multi‑region high availability—to address the restaurant sector’s operational challenges, improve customer experience, and drive data‑driven business growth.
TeleDB’s journey from a centralized MySQL/PostgreSQL‑based system to a native distributed HTAP database showcases innovations such as share‑nothing architecture, columnar storage, vectorized execution, Remote Data Access, global caching, and advanced dead‑lock detection, dramatically improving query performance, storage efficiency, and scalability.
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.
The IDC 2023 China financial industry distributed transactional database market report shows a $2 billion market, with OceanBase capturing 17.1% overall and leading local‑deployment share at 23.2%, while also dominating insurance‑securities (42.5%) and achieving strong adoption across major banks and insurers.
Vivo's unified content platform replaced its unwieldy 60 TB MongoDB store with HBase, then upgraded the cluster, introduced table‑specific connection pools, column‑only reads, tuned compaction, and leveraged multi‑version cells, cutting response times from seconds to under ten milliseconds and dramatically lowering operational costs while boosting read/write performance.
This article presents a detailed experimental study of OceanBase's Arbitration Service in a 2F1A (two full‑function replicas plus one arbitration node) configuration, examining how the system behaves when one or both full‑function replicas fail, how log‑stream degradation and permanent offline mechanisms work, and how normal service is restored after node recovery.
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 presents a comprehensive case study of TiDB deployment at Beijing Shunfeng Tongcheng Technology, covering application scenarios, TiDB features, detailed performance benchmarks, operational challenges, optimization techniques, ecosystem tools, and best‑practice recommendations for large‑scale distributed database management.
This article provides a comprehensive analysis of TiDB's PointGet operator, detailing its execution flow in the TiKV storage layer, including protobuf interfaces, read‑through lock handling, snapshot creation, MVCC logic, and the integration of the Titan plugin for large values.
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.
The OceanBase community offers a detailed, eight‑session DBA tutorial covering the platform’s architecture, deployment, migration, performance tuning, diagnostic tools, and ecosystem components, complemented by live streaming, hands‑on exercises, certification incentives, and real‑world user testimonials to help developers and DBAs master this distributed database.
This article explains GaussDB's system architecture, the roles of GTM, CN, and DN, the SQL and storage engines, parsing stages, rule‑based and cost‑based optimizers (including AI‑based techniques), distributed query plans, execution operators, and the parallel execution framework that together enable high‑performance SQL processing in a cloud‑native distributed database.
This article details the migration of a popular social app's private‑message service from a saturated MySQL cluster to PolarDB, covering business challenges, evaluation of storage‑optimization, vertical and horizontal scaling, the chosen distributed database solution, step‑by‑step offline and online migration procedures, and the resulting performance and cost benefits.
The tutorial project showcases how to implement database sharding with ShardingSphere-JDBC (versions 4 and 5) in a SpringBoot O2O order service, providing modules for sharding, a gRPC ID generator, detailed configuration of four data sources, sharding algorithms, and Swagger-based testing of order creation and queries.
OceanBase, a distributed open‑source database, offers a free e‑book and an eight‑session tutorial series covering installation, migration, operation, performance tuning, diagnostics, and ecosystem tools such as OCP, OMS, ODC, and obdiag, aimed at students, developers, and DBAs seeking practical skills and certification.
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 MatrixOne's hyper‑converged cloud‑native database architecture, detailing its three‑layer design, data execution flow, columnar storage format, metadata hierarchy, performance optimizations, compatibility mechanisms, and practical usage scenarios.
Didi replaced its Elasticsearch‑based log platform with ClickHouse, redesigning architecture into isolated Log and Trace clusters, using hourly‑partitioned MergeTree tables and aggregating views to handle petabyte‑scale writes, diverse low‑latency queries, and high QPS, achieving over 400 nodes, 40 GB/s throughput, 30 % cost savings and four‑fold query latency reduction.
To meet exploding transaction volumes, rapid innovation cycles, and strict regulatory demands, large banks are replacing mainframe core systems with distributed, horizontally‑scalable architectures, and Baidu’s GaiaDB‑X database—offering strong ACID consistency, zero‑RPO disaster recovery, and automated operations—has successfully powered core banking migrations for institutions such as Bank of China and state‑owned banks.
The article examines Oracle’s evolution from RAC‑based sharding to the 23c Global Distributed Database, highlighting its RAFT replication, cross‑region capabilities, compliance benefits, and performance advantages that position it as a true multi‑cloud, multi‑location solution for modern OLTP workloads.
The article explains why traditional MySQL sharding is problematic, introduces the open‑source distributed database TiDB, details its architecture, core features, use cases, performance benchmarks against MySQL, and provides guidance on when to adopt TiDB for large‑scale workloads.
The article explains why traditional MySQL sharding is discouraged, introduces the distributed database TiDB, details its architecture, core capabilities such as HTAP and Raft‑based consistency, compares feature support and resource usage with MySQL, and presents benchmark results demonstrating TiDB’s advantages at large scale.
This article introduces the open‑source distributed database MatrixOne, tracing its early NewSQL/MPP architecture, the challenges that prompted a major redesign, and the resulting HTAP‑oriented three‑layer architecture with decoupled compute, transaction, and storage layers, highlighting performance, cost, and scalability improvements.
This article introduces the distributed transactional KV store TiKV, explains its role as TiDB’s storage engine, details its multi‑layered architecture and Raft‑based consistency model, and discusses the performance and resource challenges encountered at massive data scales along with the engineering solutions implemented to address them.
This article details the evolution of the open‑source distributed database MatrixOne, describing its early NewSQL/MPP design, the scalability, performance and cost challenges it faced, and the architectural redesign that introduced decoupled compute, transaction, and storage layers with HTAP support using TAE, S3, and Logtail.
This article explains how Abase2 enables multi‑region deployment for a high‑scale NoSQL database by adopting CRDT technology, detailing the challenges of cross‑region consistency, the evolution of Abase's architecture, and the engineering solutions that provide Redis‑compatible CRDT command support with low latency and strong eventual consistency.
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.
The article explains Vitess's approach to generating globally unique identifiers by using dedicated sequence tables, details the underlying MySQL schema and Go implementation, and compares it with VtDriver's CAS‑based method, highlighting trade‑offs between transaction locks and lock‑free updates.
The article details how to design and implement a cloud‑native payment fund account system on Tencent Cloud, covering account definitions, fund flow and multiple account types, TDSQL storage, separated fund and account services, robust security, distributed transactions, auditing, reconciliation, and high‑availability measures for high‑concurrency merchant payments.
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.
Gaode migrated its core navigation, traffic, and financial services to OceanBase, leveraging Paxos‑based multi‑replica consistency, LSM‑Tree storage, and distributed transactions, selecting multi‑point write for massive sync workloads and central‑write for latency‑critical queries, achieving sub‑millisecond latency, significant storage savings, and a roadmap toward broader cost‑effective, serverless deployment.
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 provides a comprehensive overview of OceanBase, an open‑source distributed database, detailing its evolution, core HTAP features, multi‑tenant architecture, execution engine optimizations, advanced query optimizer, storage engine design, resource isolation mechanisms, fast import capabilities, and performance benchmarks.
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.
By adding a guard that skips the costly part‑scan in MergeTreePartsMover::selectPartsForMove when disk usage is below the threshold and no MoveTTL is set, Didi reduced BgMoveProcPool thread CPU consumption from about 30 % to under 4 %, halving overall node CPU load and improving ClickHouse’s PB‑scale performance.
Sichuan Rural Credit Union, with over 5,000 outlets and 3 billion daily transactions, migrated its core and mobile banking systems to OceanBase's native distributed database, cutting card‑issue time from 30 minutes to 5 minutes, loan processing from 3‑5 days to 1‑33 minutes, and saving more than 40% in infrastructure costs.
This article summarizes Liu Donghui’s presentation at DTCC2022, detailing Baidu Intelligent Cloud’s Redis‑compatible, high‑capacity, low‑cost PegaDB, covering its design goals, architecture, KV storage engine choices, cluster scaling, replication enhancements, performance optimizations, multi‑region active‑active support, and future roadmap.
This article details Baidu Cloud's PegaDB—a Redis‑compatible, high‑capacity, low‑cost distributed KV store—covering its design choices, architecture, performance and replication optimizations, multi‑region active‑active support, native JSON model, community contributions, and future roadmap.
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.
Ctrip evaluated and extended OceanBase Migration Assessment tools, built a one‑click migration workflow, implemented comprehensive monitoring and automatic fault‑diagnosis pipelines, and addressed compatibility challenges such as .NET charset issues and Druid parser errors, ultimately achieving a smooth MySQL‑to‑OceanBase transition.
This article explains how Apache Doris implements data sharding, partitioning (both list and range, static and dynamic), batch partition creation, and the Auto Bucket feature, providing detailed syntax, algorithms, and performance benefits for large‑scale distributed databases.
This article details Ctrip's experience migrating MySQL workloads to the distributed OceanBase database, covering the design of an assessment tool, a one‑click migration workflow, comprehensive monitoring dashboards, automated fault‑diagnosis pipelines, encountered compatibility issues, and future roadmap for the platform.
This article presents a comprehensive case study of TiDB, an open‑source distributed relational database, detailing its features, architecture, evolution within AutoHome, key business applications such as recommendation pools, financial reporting, and interactive events, as well as the automated operations and troubleshooting practices adopted to ensure high availability and scalability.
The article explains how single‑instance MySQL struggles with huge tables, resource‑starved databases, and high read traffic, and argues that sharding middleware is being replaced by modern distributed databases such as TiDB, OceanBase, Aurora, and PolarDB as the sustainable scaling solution.
The article explains how traditional single‑node MySQL faces scalability challenges such as massive tables, resource exhaustion, and read‑heavy workloads, and argues that adopting sharding, middleware, or modern distributed databases like TiDB, OceanBase, Aurora, and PolarDB is the inevitable path forward for robust data management.
The article explains the limitations of standalone MySQL, outlines common scaling problems such as oversized tables and high read traffic, and compares middleware‑based sharding solutions with modern distributed databases, highlighting why the latter are becoming the preferred choice for growing applications.
This article provides a comprehensive, step‑by‑step tutorial on setting up a local VSCode environment, configuring remote GDB, building and deploying the OceanBase observer, and performing source‑level debugging of the observer binary on Linux servers.
Dewu transitioned from a single‑instance MySQL setup to a distributed TiDB architecture—using three TiDB, PD, and TiKV/TiFlash nodes, automated backups, Prometheus monitoring, and chaos‑engineering controls—which delivered linear scalability, eliminated slow queries, cut infrastructure costs by about 58 % and maintained stable performance during major sales events.
iQIYI adopts SphereEx’s Database Mesh 2.0 by extending ShardingSphere‑JDBC and integrating the cloud‑native Pisanix proxy, creating a unified, encrypted configuration center that enables dynamic sharding, load‑balancing, read‑write separation, hot‑updates and observability, dramatically simplifying database governance and cloud migration.
This article explains how Cassandra clusters organize nodes, racks, and data centers, describes the gossip and snitch protocols, token ring architecture, replication strategies, and provides step‑by‑step commands to create, list, and delete users and roles while highlighting cross‑data‑center visibility constraints and common errors.
This article provides a detailed, step‑by‑step tutorial on installing and configuring an OceanBase 4.0 cluster on Ubuntu 22.04 using the OBD (ob‑deploy) tool, covering prerequisite hardware, required commands, configuration file creation, deployment, startup, and basic verification.
This article describes the background, architecture, and a detailed troubleshooting process for restoring a mistakenly deleted Greenplum standby data directory, including status checks, configuration cleanup, standby initialization, verification commands, and additional recommendations for handling master failures in a distributed database cluster.
CDW PG’s optimizer determines the most efficient join order for multi‑table OLAP queries by combining bottom‑up dynamic programming for smaller joins with a genetic algorithm for larger ones, while jointly selecting scan paths, join algorithms, and data‑distribution strategies to minimize execution cost.
KeeWiDB, a next‑generation distributed KV store from Tencent Cloud, combines a proxy layer, multi‑node service layer, tiered hot‑cold data placement, multi‑threaded and coroutine‑based processing, persistent memory caching, direct I/O, and enhanced replication to address Redis’s memory cost, scalability, and latency challenges.
TiDB is an open‑source, MySQL‑compatible distributed database that unifies OLTP and OLAP by using a stateless SQL layer, a Placement Driver for metadata and Raft‑managed TiKV/TiFlash storage, key‑value mapping with RocksDB, and a push‑down execution engine that splits work between coprocessor and root tasks for scalable, highly available workloads.
This article explains the TiDB rolling upgrade method, describing TiDB's architecture, key components, relevant terminology, the TiUP tool, and a step‑by‑step core upgrade workflow with code snippets and configuration adjustments to minimize service interruption.
The article reviews OceanBase's distributed relational database design, its integrated architecture, high‑compression LSM‑tree storage engine, Paxos‑enhanced two‑phase commit protocol, and how these innovations enabled the system to set successive world records in the TPC‑C benchmark, illustrating China's growing database capabilities.
TafDB, Baidu’s Spanner‑like distributed transaction database built on RocksDB and Multi‑Raft, provides a virtually unlimited metadata layer for cloud data lakes by unifying hierarchical and flat namespaces, minimizing cross‑shard transaction overhead, handling garbage collection, and employing a distributed clock, thus delivering trillion‑scale metadata capacity and tens of millions of QPS with low latency.
This article explains the motivations, challenges, and design principles of horizontal scaling for databases, using TDSQL as a case study to illustrate architecture, scaling procedures, shard key selection, high‑availability mechanisms, distributed transactions, and performance optimization techniques.
This article provides a comprehensive overview of HBase, covering its column‑oriented design, core components such as HMaster, RegionServer and ZooKeeper, the data model with column families and row keys, and detailed step‑by‑step write and read processes for distributed storage.
The article describes the motivation, requirements, and architectural design of a highly available, scalable, low‑cost distributed time‑series database built on Mimir, detailing write and read paths, multi‑tenant isolation, compaction, and the performance and cost improvements achieved after deployment.
The gpdb‑faiss‑vector plugin embeds Facebook’s Faiss library into the Dolphin (Greenplum‑compatible) engine, exposing SQL functions for distributed, high‑performance approximate nearest‑neighbor vector retrieval with caching, parallel search, configurable indexes, and sub‑millisecond latency, enabling scalable recommendation and advertising workloads.
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.
This article examines the DBLE distributed database middleware cache, reproduces a primary‑key update query that returns incomplete results due to stale routing cache, analyzes cache contents via the management console, explains the cache’s behavior and limitations, and shows how disabling the primary‑key cache restores correct query routing.
This article provides a comprehensive technical overview of OpenMLDB, covering its overall architecture, online real‑time SQL execution and storage engines, core data structures, pre‑aggregation techniques, and performance test results that demonstrate millisecond‑level latency for feature computation.
This article, based on a Flink CDC Meetup talk by OceanBase expert Wang He, introduces OceanBase’s architecture and core features, explains the implementation principles of the Flink CDC OceanBase connector, outlines its current capabilities and use cases, and discusses future enhancements and roadmap.
This article examines the challenges of ordering results in distributed databases and presents a step‑by‑step optimization that moves sorting from proxy memory to disk‑based priority‑queue processing, reducing memory pressure, disk I/O, and network waste.
This article explains how StarRocks converts a SQL statement into an optimal distributed physical execution plan, schedules the plan across compute nodes, and runs it using MPP, pipeline parallelism, and vectorized execution to achieve near‑linear performance scaling.
This article explains what an ecosystem is, defines the concept of a distributed database ecosystem, and uses TiDB as a case study to detail upstream/downstream tools, daily operation utilities, automation platforms, and emerging projects built on TiDB components, highlighting their roles and integration.
This article introduces Pegasus, a distributed key‑value store, covering its background, system architecture, double‑WAL design, performance benchmarks, recent features such as hot backup, bulk load, access control, partition split, as well as its ecosystem tools and community development plans.
This article explains what a distributed database ecosystem is, using TiDB as a case study to detail upstream/downstream tools, backup and monitoring solutions, automation platforms, and emerging projects that together form a comprehensive TiDB ecosystem.
This article provides a comprehensive overview of HBase, covering its origins, column‑family storage model, key components such as HMaster and HRegionServer, data‑location process, row‑key design strategies, practical use cases, and comparisons with relational and other NoSQL databases.
NetEase’s DBA team presents a comprehensive analysis comparing TiDB‑based innovative architecture with the traditional MySQL + DDB stack, detailing business fit, cost reduction, technical innovation, scalability, high availability, HTAP capabilities, migration strategies, and practical deployment experiences to justify adopting TiDB as a next‑generation distributed database solution.
Zhihu’s Moneta service stores over a trillion rows and faces massive write and read loads; this article explains why TiDB was chosen, how its architecture and features such as HTAP, Raft, Titan and table partitioning enable millisecond‑level query latency, high availability, and seamless scaling.
This article explores how to design a cloud‑native distributed database architecture using TiDB as a case study, discussing cost reduction, storage choices, compute‑storage separation, fault tolerance, scaling strategies, and the trade‑offs of caching and persistent storage in modern cloud environments.
The article outlines OceanBase’s evolution into an open‑source, HTAP‑capable distributed database, then details allegations that its community engaged in purchasing GitHub stars, including screenshots of incentive messages, sparking debate over the ethics of star‑inflation in Chinese open‑source projects.
This article examines the business storage requirements of large‑scale advertising platforms and details how BaikalDB was architected as a cloud‑native, MySQL‑compatible distributed database that combines OLTP, OLAP, KV and full‑text capabilities while ensuring high reliability, low cost and linear scalability.
