The article outlines the architecture, design principles, challenges, and performance optimizations of a large‑scale server monitoring system built for handling hundreds of gigabytes of data per day with high availability, low latency alerts, and multi‑platform support.
The article details how Snapdeal built a high‑performance, low‑latency ad‑serving platform that handles billions of daily requests by employing horizontal and vertical scaling, AP‑focused CAP choices, in‑memory data structures, and a suite of open‑source backend technologies.
This article outlines essential design principles—availability, performance, reliability, scalability, manageability, and cost—and practical techniques such as service separation, redundancy, partitioning, caching, proxies, indexing, load balancing, and queuing to help engineers construct high‑performance, fault‑tolerant web systems.
Caching dramatically improves website performance by storing data in memory for faster responses and reducing database load, with Memcached and Redis as popular solutions; proper routing algorithms like consistent hashing are essential to scale clusters without causing cache misses or service disruption.
This article explains how small‑team internet products evolve from a single‑server setup to a scalable, clustered web architecture by separating services, adding dedicated servers, and employing caching, CDNs, and other components to handle growing user traffic.
This article details Uber's rapid growth and the engineering choices behind its real‑time dispatch platform, covering geospatial indexing, microservice architecture, scaling techniques like Ringpop and TChannel, and strategies for availability and fault tolerance.
Although sites like Taobao appear simple to users, they rely on massive distributed search, caching, storage, load‑balancing, CDN, logging, and data‑analysis systems that demand sophisticated backend engineering, massive infrastructure, and specialized algorithms, explaining why countless top engineers are required to keep them running.
This article presents Sogou's design for a highly available, high‑performance, and horizontally scalable business platform, illustrating key architectural components and scalability strategies through a series of diagrams.
An in‑depth recap of Hong Xiaojun’s QCon presentation reveals how Meipai’s architecture evolved from a minimalist design to a highly scalable, high‑availability system, tackling MySQL bottlenecks, cache challenges, monitoring, CDN resilience, and technology migrations to support rapid growth to over a hundred million users.
During the 11.11 shopping festival Xiaomi’s push service delivered 9.65 billion messages at an average of 670 k per minute, maintaining smooth operation without congestion through a multi‑datacenter, XMPP‑based architecture with Thrift serialization and extensive caching.
The article analyzes the rapid growth of China’s 12306 online ticketing platform, the challenges of extreme traffic and concurrency during peak travel periods, and how a cloud‑native, memory‑centric architecture based on Pivotal Gemfire enabled scalable, high‑performance, and highly available ticketing services.
The talk reveals how WeChat achieved rapid growth to over 100 million users by combining precise product timing, an aggressive agile mindset, and a resilient technical backbone built on modular large‑system design, extensible protocols, gray‑release deployment, comprehensive monitoring, and fault‑tolerant disaster‑recovery strategies.
