Shopee

Series Hub: Shopee Architecture Masterclass | Next Chapter: Chapter 2 — Flash Sale Engine & Zero Overselling Answer-first: Shopee replaced its legacy Python monolith with high-performance Golang microservices orchestrated via ByteDance Kitex and Netpoll IPC to eliminate Global Interpreter Lock contention and slash memory overhead. Integrating zero-copy Protobuf serialization, partitioned Consul discovery with local DaemonSet caching, and bounded worker pools dropped internal p99 RPC latency below three milliseconds under 500,000 requests per second. ...

Previous Chapter: Chapter 1 — Microservices Foundation | Series Hub | Next Chapter: Chapter 3 — Traffic Shield: Kafka Peak Shaving Answer-first: Shopee eliminates flash-sale inventory overselling and hot-key contention by combining client purchase tokens, local memory short-circuiting, and Redis Lua atomic stock deduction with sub-key sharding. Splitting high-demand SKU inventory across randomized sub-keys prevents single Redis master saturation, guaranteeing sub-two-millisecond reservation latencies and mathematically verified zero overselling across millions of concurrent checkout requests. ...

Previous Chapter: Chapter 2 — Flash Sale Engine & Zero Overselling | Series Hub | Next Chapter: Chapter 4 — Database Scalability: From MySQL to TiDB Answer-first: Shopee defends its e-commerce infrastructure during mega shopping surges using a multi-layered traffic shield combining WAF rate limiting, virtual waiting rooms, and Apache Kafka asynchronous peak shaving. Decoupling order creation from relational persistence flattens extreme traffic spikes, preserving database stability while ensuring sub-fifty-millisecond checkout response times and zero message loss across millions of concurrent users. ...

Previous Chapter: Chapter 3 — Traffic Shield & Peak Shaving | Series Hub | Next Chapter: Chapter 5 — Full-Stack Observability Answer-first: Shopee eliminated relational database bottlenecks by migrating mission-critical checkout clusters from sharded MySQL to TiDB NewSQL distributed storage. Decoupling stateless SQL compute from Multi-Raft consensus storage across 96MB TiKV regions enables elastic scaling, automated split-merge rebalancing, and Google Percolator distributed transactions, guaranteeing sub-twenty-millisecond p99 write latency and zero data loss across availability zones. ...

Previous Chapter: Chapter 4 — Database Scalability: From MySQL to TiDB | Series Hub Answer-first: Shopee conquered telemetry scale challenges by replacing bloated Elasticsearch clusters with a high-throughput observability pipeline powered by Vector SIMD daemons, Apache Kafka, and ClickHouse columnar storage. Incorporating OpenTelemetry tail-based sampling and non-invasive eBPF continuous profiling slashes storage overhead by twelve times while retaining all system errors and anomalies with sub-one-percent runtime CPU impact. Prerequisite: Solid understanding of observability telemetry models (metrics, logs, traces), columnar database indexing (ClickHouse MergeTree), OpenTelemetry trace context propagation (W3C), and Linux kernel profiling with eBPF. ...

Answer-first: The Shopee Architecture series details how Go microservices, Redis Lua inventory reservation, Apache Kafka peak shaving, TiDB distributed SQL, and OpenTelemetry/ClickHouse observability handle 10M+ QPS and millions of concurrent buyers during 11.11 flash sales without overselling or database connection starvation. For core microservices foundations, explore our Go Microservices Production Patterns. Masterclass Overview: The Southeast Asian E-Commerce Engine Shopee is the leading e-commerce platform in Southeast Asia and Taiwan, operating across Singapore, Indonesia, Vietnam, Thailand, Philippines, and Malaysia. During annual shopping festivals (9.9, 11.11, 12.12), platform traffic surges by more than 10x within seconds at midnight, creating catastrophic load spikes that break traditional web architectures. ...