PayPay Campaign Engine: Peak Sales & Wallet Rewards

Executive Summary & Quick Answer: Scaling for billion-yen cashback campaigns requires pre-warmed Redis cluster caching, token-bucket rate limiting at the API gateway, and async queue-based payment processing to shave peak traffic spikes. Answer-first: The PayPay campaign architecture isolates high-throughput reward campaigns from core payment processing. By evaluating campaign eligibility out-of-band and writing reward points asynchronously using event queues, PayPay prevents promotional traffic spikes from impacting critical credit card processing pipelines. ...

May 5, 2026 · 8 min · Lê Tuấn Anh

Shopee Flash Sale Engine: Redis Lua & Overselling

Answer-First: Shopee prevents overselling during high-concurrency flash sales by combining local memory caching, Redis inventory sharding, and atomic Lua script decrements. This multi-tier architecture isolates hot keys in Redis memory shards and evaluates stock availability in sub-milliseconds without acquiring relational database locks. Chapter 2: Flash Sale Engine - The Mystery Behind Redis and Hot Keys ← Series hub | ← Prev | Next → Prerequisite: Read the previous article: Chapter 1: Microservices Foundation - The Power of Go, gRPC, and API Gateway. ...

May 5, 2026 · 8 min · Lê Tuấn Anh

Alipay Double 11 Operations: Full-Link Stress Test

← Series hub ← Prev • Next → Executive Summary & Quick Answer: Surviving Double 11 requires production Full-Link Stress Testing (Shadow Database traffic simulation) and automated AI-driven operational playbooks to detect and isolate degraded nodes within 1 minute. Prerequisite: Phase 2: Core Architecture (LDC, Unitization, Multi-Active) This phase is about how peak performance becomes repeatable. The core claim of Alipay’s operations team is simple: peaks are won in preparation and automation, not heroics. Under planet-scale loads, manual operational tasks fail due to human latency. Therefore, readiness must be engineered into the software stack itself. ...

May 2, 2026 · 10 min · Lê Tuấn Anh

Alipay Double 11 Scale Evolution Timeline: 2009-2026

← Series hub ← Prev • Next → Executive Summary & Quick Answer: Alipay’s Double 11 engineering journey evolved over a decade from a centralized monolithic database (2009) to a planet-scale multi-active cloud-native architecture capable of processing over 544,000 TPS at peak. Prerequisite: Executive Summary Overview Answer-First: The Double 11 evolution tracks Alipay journey from monolithic database crashes in 2009 to multi-region active-active unitized architectures. Double 11 (Singles’ Day), initiated in 2009 as a minor promotional event on Taobao Mall, evolved over a decade into the world’s largest online shopping festival. For Alipay’s engineering teams, it served as an annual crucible: a predictable yet extreme spike in transaction volume that forced the continuous redesign of payment infrastructure. This timeline tracks the evolution of Alipay’s technical scaling from a centralized database model to a modern, elastic cloud-native architecture. ...

May 2, 2026 · 10 min · Lê Tuấn Anh