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.
The article explains how Citus lets you manually propagate SQL statements to workers, shards, or placements using functions like run_command_on_workers, run_command_on_shards, and run_command_on_placements, provides concrete examples, and outlines important limitations and safety considerations.
This guide explains how to use standard PostgreSQL INSERT, multi‑row INSERT, INSERT … SELECT, COPY for bulk loading, upserts with ON CONFLICT, and UPDATE/DELETE on Citus‑distributed tables, including routing by distribution column, performance tips, and two‑phase commit considerations.
This tutorial walks through setting up Citus, creating and distributing PostgreSQL tables for a multi‑tenant ad‑analytics application, loading sample data, executing CRUD and analytical queries, and extending the approach to real‑time GitHub event analysis, demonstrating end‑to‑end database operations in a distributed environment.
This step‑by‑step guide shows how to set up both single‑node and multi‑node Citus clusters on Docker, Ubuntu/Debian, and Fedora/CentOS/Red Hat, covering repository addition, package installation, configuration of shared_preload_libraries, database initialization, worker node registration, and verification commands.
This guide shows how to combine PostgreSQL declarative time‑range partitioning with Citus distributed sharding to create a scalable time‑series database, covering table creation, distribution, automatic monthly partition generation, columnar archiving, maintenance with pg_cron, and performance benefits such as faster inserts, queries, and data expiration.
This guide walks through planning a distribution strategy, adding and back‑filling a distribution key, preparing a development Citus cluster, updating schema and queries for multi‑tenant workloads, securing connections, monitoring cross‑node traffic, and finally migrating production data using either pg_dump/pg_restore for small databases or Citus Warp for large deployments.
Citus extends PostgreSQL into a shared‑nothing distributed system where a coordinator node routes queries to worker nodes, supporting distributed, reference, and local tables, shard placement, replication modes, co‑location, parallel execution, and configurable connection‑pool settings to scale storage and CPU across a cluster.
Citus is an open‑source PostgreSQL extension that adds sharding, distributed tables and parallel query execution, enabling horizontal and vertical scaling for multi‑tenant SaaS, real‑time analytics, and massive workloads, while outlining acquisition options, practical use cases, and scenarios where it is unsuitable.
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.
This article explains the core components of TiDB—including TiKV Server, PD Server, and TiDB Server—their roles in storage, scheduling, and computation, and how the Raft consensus algorithm and TiSpark extension enable a reliable, scalable distributed database solution.
This case study details how Car Home leveraged TiDB 5.1.1 with a three‑data‑center, five‑replica HTAP architecture to support the high‑traffic 818 Global Auto Festival, covering background, business requirements, database selection, system design, performance challenges, solutions, and post‑event insights.
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.
This article introduces TiDB’s hybrid transactional‑analytical processing capabilities, explains TiKV’s region‑based storage built on RocksDB, and provides a detailed overview of RocksDB and LevelDB architectures, including their data structures, write‑read flows, and key optimizations for modern distributed database systems.
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 analyzes the evolution of Baidu's advertising data storage, detailing the business-driven requirements, the design and development of the BaikalDB distributed database, its architecture across storage, compute and scheduling layers, key features such as Raft replication and multi‑index support, and the lessons learned for building cloud‑native, high‑performance databases.
This article introduces the HR performance data preprocessing platform’s requirements, explains why HBase was selected as the storage solution, details its core concepts, architecture, data write/read processes, best practices, limitations, and presents performance metrics demonstrating its suitability for large‑scale, high‑throughput workloads.
This article explains how HBase’s distributed column‑oriented architecture, high‑performance read/write capabilities, and flexible schema make it a cost‑effective solution for handling massive, unstructured HR performance data, covering its core concepts, cluster operation, best practices, and performance metrics.
OceanBase achieved a world‑record TPC‑H performance of 15.26 million QphH, illustrating its HTAP capabilities and detailing the technical evolution, challenges, and future direction of hybrid transactional/analytical processing in modern distributed databases.
This article explains how OceanBase, a distributed relational database, achieved a new TPC‑H world record, discusses the evolution of HTAP technology, the architectural challenges of combining transactional and analytical workloads, and the future direction of the product.
OceanBase, the distributed relational database from Ant Group, set a new TPC‑H world record by leveraging its HTAP architecture, blending transaction and analytical processing, and the article details the technical evolution, challenges, and future direction of this hybrid database technology.
WeBank replaced traditional IOE systems with a Tencent‑based distributed platform using TDSQL and a unitized DCN architecture, where each Data Center Node serves a fixed user base, enabling linear horizontal scaling, fault isolation, rapid provisioning, and simplified single‑instance databases while handling billions of daily transactions.
The article traces database technology from the commercial Oracle era through open‑source and the emerging cloud‑native phase, highlights cloud as the primary battleground and the importance of the to‑B market, reviews historic academic contributions, examines Oracle and China’s TDSQL evolution, and outlines five future directions—distributed, intelligent, multi‑model, hardware‑software integration, and cloud convergence—while urging DBAs to adapt their full‑stack skills.
This article introduces the DBLE MySQL‑compatible distributed middleware, details its new pure read/write splitting feature in version 3.20.10.0, and provides a comprehensive table showing which SQL statements trigger implicit commits and their support status.
Tendis, an open‑source distributed KV store developed by Tencent, combines full Redis protocol compatibility with RocksDB persistence, a decentralized gossip‑based cluster architecture, horizontal scalability to thousands of nodes, and cost‑effective hot‑cold data mixing, making it suitable for large‑scale, high‑throughput workloads.
This article presents a comprehensive technical overview of TiDB, an open‑source distributed NewSQL database, detailing its architecture, migration strategies, and real‑world deployments across core banking, payment, wealth‑management, risk‑control, and insurance scenarios, while highlighting its HTAP capabilities and upcoming TiDB 5.0 enhancements.
This article analyzes why certain join queries in DBLE distributed database middleware fail to push down to backend nodes, leading to high CPU usage and latency, and presents four concrete examples with step‑by‑step optimizations to ensure full query push‑down and improved performance.
This article explains YugabyteDB's two‑layer logical architecture, its tablet‑based distributed storage built on Raft groups, the RocksDB‑backed local DocDB, and how it implements distributed transactions using Hybrid Logical Clocks, two‑phase commit, and MVCC, while comparing it with TiDB, CockroachDB and other rivals.
This article provides a comprehensive technical overview of YugabyteDB, covering its two‑layer logical architecture, tablet‑based distributed storage with Raft groups, RocksDB‑backed local storage design, hybrid hash‑range partitioning, and the MVCC‑based two‑phase‑commit transaction model using Hybrid Logical Clocks.
The article outlines how a call platform’s architecture progressed through successive stages—starting with a monolithic design, then business service splitting, service governance and isolated deployment, horizontal scaling, distributed database sharding, and finally micro‑service adoption—highlighting the problems each evolution solved and the new challenges introduced.
This tutorial walks through setting up a Redis Cluster on a single server with six nodes, covering node startup, handshake, slot assignment, master‑slave replication, command routing, fault‑tolerance, and practical scaling operations such as adding, rebalancing, and removing nodes.
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 summarizes a JD Cloud‑TiDB live webcast, explaining why JD Cloud chose TiDB, detailing its distributed architecture (TiDB Server, TiKV storage, PD), highlighting features such as horizontal scaling, strong consistency, real‑time analytics, backup, migration, and showcasing multiple enterprise migration case studies that demonstrate TiDB’s ability to overcome traditional database bottlenecks.
This article explains Pika’s native distributed cluster architecture, detailing its deployment structure, data distribution with tables and slots, request processing flow, both non‑consistent and Raft‑based log replication, and the enhanced metadata management that enables scalable, high‑availability storage beyond single‑node Redis limitations.
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.
The article explains the background, architecture, data distribution, processing flow, replication mechanisms, and management features of Pika's native distributed cluster, detailing how Etcd, LVS, and RocksDB are used to achieve scalable, persistent Redis-compatible storage with table isolation and flexible slot replication.
In this talk, Yun Jin explains how HBase’s petabyte‑scale, horizontally‑scalable architecture—built on Hadoop, HMaster, RegionServers, and Zookeeper—enables e‑commerce platforms to handle extreme promotion‑day traffic by supporting high‑throughput reads/writes, time‑series monitoring, massive order storage, and robust HA, while covering essential table operations, monitoring, and troubleshooting techniques.
ICBC's corporate wealth management platform, which supports trillion‑yuan assets for enterprise clients, has been migrated from a mainframe to a distributed OceanBase cluster, boosting high availability, ensuring business continuity, and cutting costs while maintaining performance and stability.
This article provides a comprehensive overview of TiDB's architecture, detailing the roles of TiKV Server, Placement Driver (PD), TiDB Server, and the TiSpark component, and explains how Raft ensures data consistency across the distributed database system.
The presentation outlines OceanBase's evolution, technical advantages such as high availability, scalability, performance, multi‑tenant HTAP capabilities, and its successful deployment in the insurance industry, demonstrating how a self‑developed distributed relational database can transform core financial services.
Three leading database experts from Tencent and cloud firms share how deep curiosity, hands‑on experimentation, persistent learning—combined with mastering distributed, cloud, and autonomous databases—forge an outstanding data craftsman, while advising newcomers to master performance, security, one DB per category, and start with open‑source tools.
The article details JD Retail's JIMKV distributed database, explaining its unified cache‑storage architecture, fault‑detection and elastic‑scaling mechanisms, hot‑cold data tiering, read/write amplification mitigation, real‑world product‑detail use case, and future plans for intelligent operations and OLAP support.
This article analyzes a community‑raised issue where a left join between a global table and a sharded table produces incorrect results in Mycat but works as expected in DBLE, explaining the underlying execution‑plan differences and how DBLE correctly merges results to avoid duplicate data.
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 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.
OceanBase, Alibaba’s self‑developed distributed relational database, achieved world‑leading TPC‑C performance in 2019 and shattered its own record in 2020, a journey marked by intense team effort, architectural innovations like Paxos‑based scalability, and a vision to become a global database leader.
TDSQL enables Tencent Meeting’s non‑disruptive, linear horizontal scaling by using a stateless SQL engine, shard‑key selection, two‑phase distributed transactions, and one‑click set expansion, delivering near‑linear performance growth, high availability, and seamless capacity increase for millions of daily users worldwide.
This article details a real‑world case of write‑hotspot performance degradation in a TiDB 3.0.9 cluster, explains TiDB’s architecture, analyzes monitoring data and hot‑region tables, and presents a redesign using varchar primary keys and SHARD_ROW_ID_BITS to disperse writes and dramatically improve latency.
The article explains how DBLE 2.19.11.0 replaces the server‑level global table check with a table‑level, Quartz‑driven mechanism that allows precise scheduling, customizable check methods, and easier result handling, and provides configuration examples for the built‑in CHECKSUM and COUNT checks.
This article examines Pharos, Everbright Bank's home‑grown HBase indexing middleware, detailing why existing secondary‑index solutions fall short, the design goals of low latency, simple architecture and non‑intrusiveness, and the concrete storage, pagination, and transaction‑consistency techniques that enable fast complex queries on massive data.
This article explains how the inventory service at a large e‑commerce platform was optimized for high‑traffic sales events by redesigning transaction handling, sharding data by SKU, and combining flexible and rigid transactions to improve throughput while preserving data consistency.
This tutorial explains how to install MariaDB's Spider storage engine, create single-table remote links, configure users and servers, and leverage Spider for sharding and multi‑server table aggregation, providing practical code examples and performance considerations for distributed database setups.
This article shares the experience of deploying TiDB on the 360 Cloud Platform, covering background challenges with massive tables, TiDB's online DDL and high‑performance features, cluster architecture, DM migration workflow, common operational issues, and detailed tuning parameters to improve latency, QPS, and resource utilization.
This article provides an in‑depth technical overview of OceanBase 2.2, covering its distributed architecture, high‑availability design, multi‑tenant resource pool, Oracle/MySQL compatibility, performance benchmarks, ecosystem tools such as OCP, ODC, OMS, and disaster‑recovery solutions for financial‑grade workloads.
This article provides a comprehensive technical overview of TiDB, covering its HTAP design, TiKV storage engine with RocksDB and Raft replication, the mapping of relational tables to key‑value pairs, MVCC implementation, transaction handling, and the PD scheduler that balances replicas, leaders, and hot spots across a distributed cluster.
This article summarizes a Cassandra meetup presentation that traces the database's origins from BigTable and Dynamo, outlines its key milestones, explains its peer‑to‑peer and LSM architecture, highlights current features, real‑world deployments, performance advantages, and previews upcoming 4.0 releases and community projects.
This article details how 360 adopted Cassandra for its cloud drive, describing Cassandra’s decentralized architecture, the reasons for its selection over HBase, large‑scale deployment challenges, performance optimizations, reliability improvements, disk utilization techniques, and the evolution of the system from 2010 to present.
This article details Zhihu's read‑service architecture, its massive data scale and performance challenges, early Bloom‑filter and HBase solutions, the design goals of high availability, high performance and scalability, and the subsequent migration from MySQL to TiDB with cloud‑native practices.
Lindorm, an Alibaba‑derived distributed NoSQL database built on HBase, delivers multi‑model hybrid storage, five‑fold throughput gains, sub‑millisecond latency, advanced indexing, cloud‑native elasticity, strong/adjustable consistency, and comprehensive security and multi‑tenant features for massive data workloads.
This article details the AutoHome community's migration from a monolithic SQL Server database to the distributed TiDB platform, covering the performance bottlenecks that prompted the change, the evaluation of candidate databases, extensive OLTP/OLAP testing, the full‑ and incremental‑sync migration strategy, rollback mechanisms, and the resulting operational improvements.
This article details the challenges and solutions encountered when migrating Fengchao's high‑throughput payment platform—handling over a hundred‑billion rows and millions of QPS—from a sharded MySQL architecture to TiDB, covering performance bottlenecks, TiDB advantages, migration steps, tooling, pitfalls, and optimization recommendations.
OceanBase’s distributed relational database achieved the top TPC‑C benchmark score by leveraging cloud‑native resources, optimized storage, advanced transaction engines, and extensive SQL tuning, with detailed insights into preparation, system architecture, performance testing phases, ACID compliance, and storage optimizations that set new industry standards.
OceanBase’s TPC‑C benchmark demonstrates how its distributed database achieves high durability, atomicity, isolation, and consistency on commodity cloud servers using Paxos‑based log replication, two‑phase commit, MVCC, and replicated tables, highlighting the architectural challenges and solutions for ACID compliance.
This article explains how OceanBase’s distributed, shared‑nothing architecture, with dual data replicas, Paxos‑based consistency, online compression, and resource‑isolated compaction, enables it to achieve top TPC‑C performance while addressing storage costs and CPU usage.
This article provides a comprehensive technical analysis of OceanBase’s record‑breaking TPC‑C benchmark, covering the preparation work, test system design, planning, performance testing methodology, ACID verification, and the lessons learned from achieving 60.88 million tpmC on a distributed cloud platform.
This article provides a detailed technical analysis of OceanBase’s TPC‑C benchmark performance, covering the database’s development history, benchmark methodology, identified shortcomings, future improvement plans, and the strict standards and audit processes that ensure reliable OLTP benchmarking results.
OceanBase, the distributed database from Ant Financial, topped the latest TPC‑C benchmark, and this article explains the benchmark’s significance, the rigorous certification process, the performance and cost metrics, and how OceanBase’s architecture and Alibaba Cloud support enabled this achievement.
This article provides a comprehensive overview of Apache Cassandra, covering its origins at Facebook, key architectural features such as distributed design, elastic scalability, tunable consistency, and high availability, as well as typical deployment scenarios and notable companies that use it.
This article explains how CB‑SQL implements follower reads by using safe (closed) timestamps, describes the CT update mechanism with a Minimum Proposal Tracker, and discusses routing, replica read validation, timestamp forwarding, range split/merge handling, and recovery strategies for consistent distributed reads.
The article describes how Tencent Financial Technology (FiT) built a globally largest, financial‑grade distributed MySQL cluster with multi‑active data‑center architecture, Raft‑based failover, priority‑driven switching, and automated backup to achieve 99.999% availability for massive payment workloads.
The article explains CB‑SQL’s distributed changefeed architecture, its CDC implementation, the challenges of horizontal scalability and transactional ordering, and the innovative RangeFeed mechanism that enables ordered row‑level streams, resolved timestamps, and seamless integration with external systems like Kafka.
WeBank adopted Tencent TDSQL, a MySQL‑based distributed database with strong‑consistency replication, auto‑sharding, read/write separation, automatic failover, and a management platform; deployed across two IDC regions using a 3+2 replica model, supporting petabyte data, billions of daily transactions, and high availability.
This guide walks through the complete process of building a highly available MySQL cluster by installing DBLE middleware on three nodes, configuring a ZooKeeper ensemble to coordinate the DBLE instances, and verifying the setup with configuration reloads, view synchronization, and fault‑tolerance tests.
This article recounts TiDB’s evolution from a transactional MySQL‑compatible database to a hybrid‑transactional/analytical platform, detailing its architecture, performance challenges, integration with TiSpark and TiFlash, and future plans to balance TP and AP workloads.
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.
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.
The article introduces CB‑SQL, JD Retail’s next‑generation elastic database based on CockroachDB, and comprehensively explains its overview, layered architecture, storage replication, cluster management, MVCC, hybrid logical clocks, lock‑free distributed transactions, CDC changefeeds, and SQL interface support.
In this interview, senior director Han Hongyuan of Ant Group discusses OceanBase's award-winning innovations, core financial focus, competitive strengths, distributed architecture improvements, compatibility efforts, milestone developments, and future challenges in cloud‑native and database technology.
This article, based on a 2019 Ant Financial technology summit talk, details Net Business Bank’s adoption of the financial‑grade distributed database OceanBase, covering its logical and physical architectures, migration services, high‑availability designs, elastic data sources, and future outlook for distributed database innovation in banking.
QTSDB is a distributed time‑series database built on InfluxDB that adds cluster capabilities such as horizontal scaling, replica fault‑tolerance, sharding, meta‑service coordination, and comprehensive read/write processing, while also detailing failure recovery and node expansion strategies.
This article details the Industrial and Commercial Bank of China's multi‑year migration from mainframe‑based DB2 to a high‑availability, distributed MySQL solution, covering the challenges, strategic decisions, technical stack, containerization, operational improvements, and measurable business outcomes.
This article details the Industrial and Commercial Bank of China's migration from traditional OLTP mainframe databases to a large‑scale, high‑availability MySQL distributed architecture, covering challenges, strategic goals, technology selection, implementation phases, performance improvements, and future directions.
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.
OceanBase, Alibaba’s home‑grown distributed relational database, survived early skepticism and near‑disbandment to replace Oracle in Ant Financial’s core systems, achieve record‑breaking transaction throughput, and now powers dozens of Chinese banks, illustrating the challenges and triumphs of building a modern DBMS.
This article provides a comprehensive technical overview of TiDB's architecture, its SQL optimizer—including logical and physical optimization phases, rule‑based transformations, join ordering, and statistics collection—and outlines future work to improve query planning stability and performance.
This article introduces Apache ShardingSphere’s ecosystem, core sharding and governance capabilities, access endpoints such as Sharding-JDBC, Sharding-Proxy and Sharding-Sidecar, and details JD.com’s real‑world implementation, including data‑sharding strategies, distributed primary keys, hint routing, performance optimizations, and future roadmap.
The inaugural TVP Training Camp on March 16 2019 in Beijing gathered Tencent Cloud’s TVP members and leading big‑data experts to discuss emerging technologies such as Greenplum, PMEM‑driven infrastructure, data‑operation optimization, and next‑generation cloud databases, while a round‑table addressed practical challenges and affirmed Tencent’s commitment to ongoing expert collaboration.
Fusion is Didi’s self‑developed distributed NoSQL database, fully compatible with the Redis protocol, that combines Redis‑level low latency, MySQL‑level durability, ACID transactions, multi‑replica high availability, FastLoad bulk import, NewSQL secondary indexes, and cross‑datacenter active‑active replication to serve petabyte‑scale ride‑hailing data.
OceanBase, a fully proprietary distributed NewSQL database, has evolved over eight years to support high‑availability, strong consistency via Paxos, flexible replica management, OBProxy routing, LSM‑Tree storage, and migration tools, enabling seamless scaling, disaster recovery, and Oracle compatibility for large‑scale financial services.
This article examines TiDB, a world‑class open‑source distributed NewSQL database, comparing its transaction and query behavior with MySQL, discussing underlying Percolator model, server‑side prepared statements, batch processing techniques, and practical optimization strategies for developers.
The article outlines Ant Financial's three‑generation database architecture evolution, the challenges of upgrading legacy commercial databases, and introduces the OceanBase Migration Service (OMS) as a comprehensive, automated solution that enables seamless, low‑risk migration to a distributed cloud database with rapid validation, data verification, and one‑click cut‑over capabilities.
This article explains how OceanBase 2.0’s partitioning architecture, partition‑group feature, and a series of performance optimizations enabled Ant Group’s payment core to handle millions of transactions per second during the Double‑11 shopping festival, while also describing the system’s advantages, results, and future capabilities.
