This article analyzes Bilibili's private messaging architecture, identifies performance bottlenecks such as MySQL slow queries, storage limits, and tightly coupled services, and presents a multi‑layer redesign with caching, sharding, BFF separation, and consistency mechanisms to sustain tenfold traffic growth.
This article walks through the step‑by‑step evolution of a Java‑based e‑commerce system—from a single‑server monolith to a fully distributed architecture with load balancing, read/write separation, caching, sharding, and service decomposition—highlighting the motivations, challenges, and key design decisions at each stage.
In September 2020 JD Digital launched a comprehensive, scientifically driven preparation for the 11.11 shopping festival, mobilizing 19 cross‑functional teams to execute capacity planning, disaster recovery, performance optimization, encryption upgrades, and coordinated stress‑testing to ensure a stable, secure, and high‑performance system for the massive sales event.
This article walks through the step‑by‑step evolution of a Java‑Web e‑commerce system—from a single‑server monolith to clustered services, read‑write separation, search integration, caching, sharding, and finally service decomposition—highlighting the architectural decisions and challenges at each stage.
This article recounts how a pandemic‑era live‑streaming service rapidly expanded from ten‑thousand to one‑million concurrent viewers within three days by analyzing the pre‑deployment assessment, container‑based scaling, monitoring, emergency response plans, and post‑launch optimizations.
The article details how JD’s advertising division tackled the massive traffic surge of the 11.11 shopping festival by expanding shard capacity, optimizing models and data pipelines, migrating workloads to the cloud, and implementing cost‑saving measures that together ensured stable, high‑performance ad delivery.
The article details how 7FRESH's R&D, testing, network operations, and product teams coordinated system capacity expansion, degradation mechanisms, emergency response procedures, extensive performance testing, and 24/7 monitoring to ensure stable and scalable service during the high‑traffic 11.11 shopping event.
During the 2019 Chinese New Year Gala, Baidu mobilized a massive technical operation—scaling cloud resources, isolating traffic, and deploying AI‑driven security—to flawlessly process over 9 billion red‑packet interactions despite unprecedented traffic spikes and login surges.
Over ten years of Alibaba's Double 11, the company transformed a modest marketing event into a global e‑commerce platform by continuously improving backend architecture, scaling strategies, full‑link stress testing, multi‑active data centers, cloud migration, and real‑time incident response, offering valuable operational insights.
This article details Dangdang's 15‑year evolution from a monolithic system to a distributed, SOA‑based architecture, outlining the challenges of high‑traffic e‑commerce events and the strategies—system grading, decoupling, asynchronous processing, batching, and rate limiting—used to achieve reliable, scalable operations.
This article recounts how a rapidly growing online platform transformed a tightly coupled, fragile architecture into a scalable, high‑availability system by applying dynamic/static separation, read‑write splitting, caching, load‑balancing, intelligent monitoring, and finally migrating to a micro‑service architecture.
During the 2015 Double 11 shopping festival, Suning’s IT team combined big‑data‑driven capacity planning, system tiering, stress testing, architecture review, comprehensive monitoring, and emergency response mechanisms to achieve a 358% increase in total orders, with mobile sales up 67% and offline growth of 153%.
This article examines how leading Chinese e‑commerce platforms such as Dangdang, Suning, Mogujie, and Vipshop redesign their backend systems, adopt decoupling, caching, scaling, and monitoring techniques to handle the massive traffic spikes of the Double‑11 shopping festival.
