This article explains the concepts of local and global indexes in OceanBase, demonstrates how to create tables and indexes, compares six practical scenarios—including no index, local index, partitioned queries, unique and global indexes—and provides performance metrics to guide database optimization.
This article investigates why Oracle and OceanBase return different results when querying the USER_TAB_COLUMNS view in stored procedures, demonstrates reproducible tests, analyzes system view behavior, and proposes workarounds such as using ALL_TAB_COLUMNS, creating synonyms, intermediate tables, or materialized views to ensure consistent table name retrieval.
This article provides a comprehensive overview of OceanBase's HTAP capabilities, detailing its core features, technical architecture, execution and storage engines, resource isolation, fast import mechanisms, performance benchmarks, and future enhancements, supported by diagrams and real‑world deployment data.
This article describes a real‑world OceanBase failure scenario where a core dump fills the data disk, and provides a step‑by‑step guide to shrink datafiles to 80% of disk capacity, adjust parameters, reduce tenant replicas, offline and reinstall OBServer instances, and finally restart the cluster.
This article demonstrates how to configure transparent encryption in OceanBase 4.1.0.0 Enterprise, create encrypted and non‑encrypted tables, perform major merges, and use the ob_admin dumpsst tool to inspect macro blocks, confirming that encrypted data is not readable while non‑encrypted data is visible.
The Aikexing Open Source Community weekly newsletter shares curated database articles, technical insights on MySQL, OceanBase, and Redis, announces SQLE 2.2309.0‑pre2 release with Feishu integration, recaps recent events like QCon Beijing, and promotes upcoming meetups and open‑source projects.
This article analyzes the MySQL ERROR 1499 caused by exceeding partition limits in OceanBase, examines server parameters, recycle‑bin settings, and tenant memory usage, and provides calculations and recommendations to expand memory or limit partition counts to prevent the error.
This guide explains how to prepare the environment, enable SSL transport encryption for OceanBase OBServer and ODP via OBProxy, configure certificates and whitelist settings, and verify the encryption using MySQL and RPC ports, while highlighting common pitfalls and reference links.
This article explains how to use Shell scripts together with Excel VLOOKUP to extract OceanBase cluster Parameters, Variables, and ProxyConfig values, compare them against default or DBA‑tuned settings, and generate a report that highlights unexpected configurations for manual verification.
The SQLE 2.2308.0-pre2 release introduces zero‑cost Java integration, TiDB abort‑release support, OceanBase for Oracle data source handling, and a comprehensive set of documentation, demo links, optimizations, and bug fixes for both community and enterprise editions.
This article explains the physical layout of OceanBase's clog directory, the roles of log_pool and tenant_id sub‑directories, how log disk capacity is allocated via configuration parameters, the concept of meta tenants and log streams, and provides scripts for monitoring clog usage and disk utilization.
The SQLE 2.2308.0-pre1 release introduces community and enterprise enhancements such as intelligent SQL file scanning, per‑instance workflow approver matching, and the ability to abort deployments on OceanBase and TDSQL data sources, accompanied by usage examples, command‑line instructions, and full release information.
This article examines the differences between MySQL's stop slave and reset slave all commands and OceanBase's replication controls, presenting experimental results that show how clog synchronization affects cluster availability, data consistency, and the procedures for decoupling standby clusters.
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 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 investigates why OceanBase's memory freeze threshold changes during load testing by analyzing monitoring data, inspecting the relevant source code, and demonstrating debugging steps, ultimately revealing that the threshold is computed dynamically based on real‑time memory usage and can be lowered when other memory modules consume space.
This article analyzes a puzzling OceanBase data‑type implicit conversion problem where UPDATE statements intermittently fail with SQL syntax errors while SELECT statements return unexpected results, explains the underlying conversion mechanisms, shows diagnostic queries and log excerpts, and provides practical recommendations to avoid such errors.
This article provides a step‑by‑step guide on how to replace OceanBase Cloud Platform (OCP) nodes using the ANTMAN tool, covering environment preparation, configuration adjustments, execution of management scripts, tenant migration, cleanup of old services, and troubleshooting tips for a seamless database cluster upgrade.
This article compares OceanBase (MySQL mode) and MySQL in terms of user management, password syntax, user locking, permission levels, grant statements, grant tables, network white‑list access control, row‑level security, and role management, highlighting similarities, differences, and migration considerations.
This article explains OceanBase's MySQL‑compatible security features, covering the MAPI authentication process, user naming conventions, password complexity and expiration settings, and mechanisms for handling repeated login failures, with detailed comparisons to MySQL.
This weekly newsletter curates top industry tech articles covering SQL deployment capabilities, MySQL replication issues, LLM‑to‑SQL benchmarks, connection limit errors, OceanBase tracing, and provides an open‑source SQL quality management platform update with development progress and upcoming plans.
This article presents a comprehensive performance comparison of OceanBase with MySQL and TiDB, details step‑by‑step deployment of OceanBase (both single‑node and cluster), explains configuration and resource‑pool management, and shares practical migration techniques and troubleshooting tips for production workloads.
This article explains why AUTO_INCREMENT is unsupported in OceanBase Oracle tenants, introduces four practical ways to implement auto‑increment columns using sequences, DML, DDL, triggers, and the GENERATED BY DEFAULT AS IDENTITY syntax, and provides step‑by‑step SQL examples for each method.
This article explains how to customize the OBClient client’s welcome output by installing dependencies, cloning the OceanBase OBClient source, editing specific source files to replace default strings, recompiling the client, installing the new package, and verifying the changed prompts.
This article consolidates practical experience and author insights to guide OceanBase engineers in quickly diagnosing and resolving slow‑SQL performance issues by leveraging ODP and OBServer logs, key metrics, and systematic analysis steps.
The article investigates why pure‑read QPS drops significantly after bulk updates in OceanBase, reproduces the issue with a sysbench workload, analyses flame‑graph and SQL audit data, explains the LSM‑Tree read‑amplification mechanism, and proposes practical mitigation steps such as major freeze, plan binding, index creation, and the queuing‑table feature.
This article explains OceanBase's write throttling feature, describing the two main parameters, the internal implementation logic, source‑code analysis, configuration steps, and practical usage scenarios for controlling write speed and ensuring system stability.
This article explains how to verify whether OceanBase's freeze mechanism and memstore dump processes are functioning correctly by querying internal tables, inspecting logs, and checking related metrics such as active_memstore_used, major_freeze_trigger, and MemTable reference counts.
In a keynote at the first OceanBase Developer Conference, Professor Zhou Aoying outlines the evolution of database technology, its role as a foundational data‑power platform, the importance of benchmarks for distributed databases, and the vision for a unified Data Power Platform in China’s digital economy.
This guide explains how to use the OceanBase server_permanent_offline_time parameter to permanently offline a faulty node, rebuild its data, and restore normal operation, including preparation, command steps, verification, and recommended settings for production.
This article explains how OceanBase's recycle bin works, covering error causes when flashing back tables, methods to obtain a table's database, handling of multiple same‑name tables, visibility across tenants, and the ability to flash back tables or tenants even after the recycle bin is disabled.
This article explains how the default PL/SQL delimiter '/' in OceanBase Oracle tenants conflicts with division operators, causing syntax errors, and demonstrates fixing the issue by changing the delimiter to '//' with detailed code examples and execution results.
The article explains the concepts, differences, and practical usage scenarios of local (partition‑aligned) and global indexes in OceanBase, providing SQL examples for queries with and without partition keys and guidance on creating unique indexes using either index type.
This article explains the background, environment setup, overall process, and detailed SQL commands required to safely lock, kill sessions, and permanently delete a MySQL tenant in OceanBase, including optional recycle‑bin handling.
The article explains what OceanBase BUFFER (Queuing) tables are, why frequent bulk updates cause performance degradation, and provides three optimization methods—including binding execution plans, manual data transfer, and setting table_mode='queuing'—with concrete MySQL and Oracle examples and query scripts to monitor merges.
This article explains how to delete tenants in OceanBase, covering immediate and delayed deletion, recycle‑bin handling, relevant SQL syntax, parameter settings, and recovery procedures, with detailed command examples and status explanations.
This article explains the LSM‑Tree foundation of OceanBase, details its tiered and leveled compaction strategies, and presents two experiments that observe Mini and Minor compactions under different configuration parameters, revealing how minor freeze and trigger settings affect data movement between L0 and L1 layers.
This article explains OceanBase's three tenant deletion approaches—normal, delayed, and immediate—detailing the DROP TENANT syntax, recycle‑bin behavior, and providing step‑by‑step SQL examples for creating, dropping, restoring, and permanently removing tenants.
This article provides a step‑by‑step guide for scaling an OceanBase cluster, covering both white‑screen and black‑screen methods to add zones (replicas) and resources (OBServers), including configuration file preparation, deployment commands, zone addition, verification queries, and procedures for both expansion and contraction.
This article examines how session IDs are derived for the kill command in OceanBase, compares IDs obtained through show processlist, information_schema.processlist, and oceanbase.__all_virtual_processlist, and demonstrates methods to terminate all connections of a specific tenant across different observers and obproxies.
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 provides a comprehensive step‑by‑step tutorial on deploying OceanBase in a single‑node environment, covering resource unit, resource pool, and MySQL‑type tenant creation, modification, deletion, user management, and relevant system data dictionary tables, with full SQL command examples.
This article explains how to create and use control files with the obloader tool to import and export data in OceanBase, covering template syntax, practical examples, common errors, and multiple solutions for handling column mismatches and data preprocessing.
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 guide walks through preparing the environment, building and launching the OceanBase Config Server, registering it with an OB server cluster, installing and configuring OBproxy, and includes troubleshooting tips for common connection issues.
This article demonstrates how to deploy OceanBase 4.X in a minimal single‑node configuration, explains the key resource parameters, provides the necessary YAML configuration and command‑line steps to start the server, create a MySQL‑compatible tenant, and verify resource usage and basic database operations.
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.
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 weekly digest curates top industry technical shares, featuring articles on database cloud migration, MySQL hash join evolution, OceanBase distributed query performance, MySQL subquery execution, and the latest SQLE SQL audit tool release, along with community development progress and upcoming plans.
This article details a step‑by‑step troubleshooting process for an OBproxy deployment error where a client loses connection to the OceanBase server due to an incorrect port in the root service list, including environment setup, command examples, log analysis, and the final resolution.
This article compares the architectures of OceanBase and TiDB, explaining how their sharding and compute‑storage separation designs affect high availability, latency, and workload suitability, and offers guidance on selecting the right distributed database for complex enterprise applications.
This article explains the types and formats of OceanBase logs, how to identify relevant log files, interpret log fields such as trace_id, lt, and dc, and provides step-by-step methods for using error codes and trace IDs to pinpoint the root cause of errors.
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.
The article explains why the free command reports more memory than the available column, describes how the kernel calculates MemAvailable using min_free_kbytes and watermarks, and provides practical guidance on tuning min_free_kbytes to meet OceanBase's memory requirements.
The preview release SQLE 1.2209.0-pre1 introduces OceanBase TopSQL auditing, Alibaba Cloud RDS MySQL audit‑log support, and a sub‑query nesting rule, while providing project background, download links, demo environments, and a detailed list of new features and release notes for database professionals.
The SQLE 1.2208.0 release introduces intelligent scanning for Alibaba Cloud RDS MySQL slow logs, adds numerous MySQL audit rules, opens enterprise‑level rules to the community, provides new OceanBase for MySQL audit rules, a reporting statistics page, PostgreSQL analysis support, and several scenario‑based audit enhancements along with many optimizations and bug fixes.
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.
The article examines the growing demand for HTAP databases, comparing cloud‑native solutions such as Google AlloyDB, Oracle MySQL HeatWave, Amazon Aurora, and domestic offerings like TiDB and OceanBase, analyzing their architectures, offload mechanisms, performance claims, and trade‑offs for mixed OLTP/OLAP workloads.
The SQLE 1.2208.0-pre1 release introduces a preview version of the SQL audit tool with project details, new OceanBase for MySQL audit rules, PostgreSQL plugin SQL analysis, a complete list of release notes, optimizations, and bug fixes, all aimed at enhancing database security and usability.
The SQLE 1.2207.0 release introduces a redesigned dashboard, incremental intelligent scanning for slow‑log and TiDB audit logs, OceanBase MySQL‑mode audit plugin, JetBrains IDE audit plugin, along with numerous optimizations, bug fixes, and detailed release information for both community and enterprise editions.
The SQLE 1.2207.0‑pre1 pre‑release introduces OceanBase MySQL‑mode audit plugins, exclusive OceanBase rules, enhanced table‑name case checks, count(*) recommendations, adds TiDB audit‑log support, fixes several MySQL‑related bugs, and outlines future plans for more OceanBase and Oracle‑mode auditing capabilities.
This article examines the most common Chinese distributed database architectures, comparing integrated SHARDING designs like OceanBase with separated compute‑storage models such as TiDB and SQL‑proxy based systems, highlighting their inherent trade‑offs, performance challenges, and practical considerations for choosing the right solution.
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.
The presentation details Alipay's evolution through three stability phases—capacity, elastic cloud‑native architecture, and green computing—covering unit‑based deployment, elastic scaling, ServiceMesh, full‑chain load testing, intelligent monitoring, and the OceanBase distributed database, illustrating how these techniques achieved 99.99% availability during the 2021 Double‑11 peak.
The article examines the strikingly similar development trajectories of electric vehicles and distributed databases, tracing their historical origins, technological challenges, market dynamics, and recent breakthroughs such as Tesla's autonomous electric cars and OceanBase's native HTAP capabilities, while highlighting the role of open‑source and scaling strategies.
This article explains how Ant Financial’s Alipay scales to hundreds of thousands of transactions per second during Double 11 by using logical data centers (LDC), unitized architecture, CAP theorem analysis, OceanBase database, and multi‑region disaster‑recovery strategies.
The article explains how Ant Financial scales Double‑11 payment traffic to hundreds of thousands of TPS by employing logical data centers (LDC), unit‑based system design (RZone, GZone, CZone), database sharding, CAP theorem analysis, Paxos‑based consensus, and the OceanBase distributed database, while also detailing disaster‑recovery and traffic‑shifting mechanisms.
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.
The article explains how Ant Group’s Alipay handles massive double‑11 payment traffic by using logical data centers (LDC), unit‑based architecture with RZone, GZone and CZone, traffic routing, disaster‑recovery strategies, and a CAP‑aware design built on the OceanBase distributed database.
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.
This article explains how Ant Financial’s payment system grew from 20,000 transactions per minute in 2010 to 540,000 TPS in 2019 by adopting logical data centers (LDC), unitized architecture (RZone, GZone, CZone), OceanBase’s Paxos‑based consensus, and sophisticated traffic steering and disaster‑recovery strategies.
This article dissects Alipay's massive Double‑11 payment surge, explaining how its Logical Data Center (LDC) and unit‑based architecture—RZone, GZone, and CZone—scale to hundreds of thousands of transactions per second, manage traffic routing, implement disaster‑recovery, and navigate the CAP theorem using OceanBase and Paxos.
In 2020 OceanBase achieved a world‑record TPC‑C benchmark of 7.07 billion tpmC, spun off as an independent company, attracted dozens of marquee customers, built a four‑layer ecosystem, delivered ultra‑high performance for enterprises, and introduced Paxos‑based disaster‑recovery that guarantees RPO = 0 and minute‑level RTO.
This article explains how Ant Financial’s logical data center (LDC) architecture uses unitization, database sharding, and CAP‑aware design—including RZone, GZone, and CZone—to achieve tens of millions of TPS during Double‑11, while providing multi‑active disaster recovery and high availability.
This article analyzes the massive traffic handling of Alipay during Double 11, explaining the LDC (Logical Data Center) unit‑based design, the RZone‑GZone‑CZone hierarchy, traffic steering, disaster‑recovery mechanisms, and how OceanBase and Paxos enable CAP compliance for ultra‑high‑availability payments.
This article explains how Ant Financial’s logical data center (LDC) architecture, based on user‑sharded RZones, GZones, and CZones, combined with OceanBase’s Paxos‑based consensus, enables massive horizontal scaling, high availability, and disaster‑tolerant processing of over half a million payment transactions per second during Double‑11.
The article explains how Ant Financial’s Logical Data Center (LDC) and unit‑based architecture, combined with sharding, CAP analysis, and OceanBase’s Paxos‑based consensus, enable the payment platform to sustain tens of millions of transactions per second during Double‑11 events while ensuring high availability and disaster recovery.
In the eighth episode of the MySQL冲冲冲 live series, experts discuss the rise of Chinese domestic databases such as TiDB, OceanBase, and Jusheng, comparing their architectures, ecosystems, and market prospects while reflecting on the broader implications for MySQL‑based distributed systems.
The CNCC 2020 Database Industry Collaboration Forum in Beijing brings together leading experts and academics to discuss OceanBase’s distributed relational database successes, industry‑academia partnership models, and strategies for cultivating database talent through joint research, training, and ecosystem development.
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.
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.
This article analyzes the features, performance benchmarks, market share growth, and use‑case scenarios of Alibaba Cloud's PolarDB, OceanBase and other services alongside Tencent Cloud's MySQL, CynosDB and related offerings, highlighting how each provider positions its cloud database portfolio in China’s fast‑growing market.
This article explains how Ant Financial’s logical data center (LDC) and unitized architecture, combined with OceanBase’s Paxos‑based consensus, enable the massive TPS growth for Double‑11 payments while addressing sharding, CAP trade‑offs, traffic diversion, and multi‑site disaster recovery.
The article explains how Alipay achieves massive payment throughput during Double‑11 by using logical data centers (LDC), unit‑based system design, multi‑active disaster‑recovery, and CAP‑theorem analysis, highlighting the role of OceanBase and PAXOS in ensuring consistency and availability.
This article chronicles the ten‑year evolution of OceanBase, a distributed relational database created by Sun Zhenkun and his team, detailing early challenges, technical breakthroughs, benchmark victories like TPC‑C world records, and its impact on Alibaba’s financial systems.
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.
OceanBase achieved a new TPC‑C world record of 707 million tpmC using 1,557 cloud servers, demonstrating near‑linear horizontal scalability, significant single‑node performance gains, efficient parallel query processing, and a markedly lower cost per transaction compared with traditional high‑end hardware solutions.
This article explains how Ant Financial’s LDC (Logical Data Center) architecture, unitized RZone/GZone/CZone design, OceanBase database, and CAP-aware strategies enable the payment platform to handle double‑11 traffic peaks of over 540,000 transactions per second while ensuring high availability, disaster recovery, and eventual consistency.
This article explains OceanBase's public‑cloud deployment, its unique architecture without a central controller, horizontal scaling via partition groups, LSM‑Tree storage design, advanced SQL engine features, ACID‑plus‑Availability guarantees, and real‑world performance records, illustrating why it suits high‑availability financial workloads.
This article explains how Ant Financial’s massive Double‑11 payment traffic is handled through logical data centers (LDC), unit‑based architecture (RZone, GZone, CZone), traffic routing, disaster‑recovery strategies, and a CAP analysis that highlights the role of OceanBase’s Paxos‑based consensus in achieving high availability and eventual consistency.
The article summarizes Xu Wenqi's 2019 Alibaba Cloud Summit talk on Ant Financial's distributed architecture, covering the shift from monolithic to microservices, modular development, load‑balancing, database sharding, the distributed TA system, task scheduling, gray‑release, full‑link stress testing, and OceanBase high‑availability solutions.
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 reviews the historical evolution, market size, and technical advantages of relational databases, explains the shift from centralized to distributed architectures, and highlights OceanBase's recent breakthroughs and community events as a modern distributed relational solution.
The author recounts his first year at Alibaba, detailing the transition from a solo newcomer to leading the OceanBase cloud platform, establishing large‑scale real‑time monitoring with JStorm, evolving team processes, and adapting to Alibaba’s fast‑paced, iterative culture.
The article explains how Alipay’s Logical Data Center (LDC) architecture, with its RZone, GZone, and CZone unitization, combined with OceanBase’s Paxos‑based consensus, enables massive TPS growth, traffic diversion, and disaster‑recovery while navigating the CAP theorem constraints.
The talk reviews the evolving challenges of enterprise databases, the shift toward distributed and cloud‑native architectures, and how OceanBase addresses high availability, scalability, hardware independence, and performance standards such as TPC‑C to meet modern financial and enterprise workloads.
The article presents a detailed technical overview of OceanBase, explaining why traditional centralized databases cannot meet modern OLTP and OLAP demands, how OceanBase achieves distributed transaction processing with Paxos‑based replication and majority voting for high availability, and how it validates its capabilities through the TPC‑C benchmark.
Alibaba Cloud’s CTO explains how the company’s fully self‑developed cloud platform—featuring the Feitian operating system, Shenlong servers, OceanBase and PolarDB databases, RDMA networking, and a custom AI chip—handled the record‑breaking 2019 Double 11 traffic of 2.684 trillion yuan, 54.4 k orders per second, and 970 PB of data.
