RocketMQ

Alipay Double 11: 544,000 TPS Architecture Explained Research Baseline Two different Double 11 peak figures circulate widely, and they measure different layers of the stack — conflating them is the most common error in write-ups on this topic: Figure What it actually measures Layer Source 544,000 TPS Alipay payment transactions per second (2019) Payment / ledger OceanBase engineering 61 million QPS Database queries per second at the same 2019 peak Database OceanBase engineering 583,000 orders/sec Order creation on Alibaba’s e-commerce platform (2020) Commerce / order intake Alibaba Group press release [!IMPORTANT] The widely-quoted 583,000 figure is order creation throughput on Alibaba’s commerce platform, not Alipay’s payment TPS. Alipay’s reported payment peak is 544,000 TPS. This article is about the payment-side architecture, so 544,000 TPS is the relevant number. ...

← Series hub ← Prev • Next → Answer-first: Alipay’s Double 11 technology deep dive reveals high-performance internals: binary Bolt RPC protocol multiplexing over single TCP streams, RocketMQ 2PC transactional messaging for async decoupling, OceanBase LSM-tree compaction tuning, and multi-zone Paxos quorum consensus to achieve 544,000 TPS payment processing. Prerequisite: Phase 4: Technology Overview This document is a deep-dive companion to Phase 4. It focuses on the internal mechanics that define the hard limits of peak performance systems: RPC protocol layouts, consensus log replication pipelines, storage engine compaction configurations, and distributed transactions. ...