The Essence of Architecture and Scaling Strategies in Large‑Scale Web Systems – A Weibo Case Study

Before discussing the essence of architecture, the author reflects on the magnitude of million‑level traffic, using Uber’s daily order volume as an illustration of scale and the need for strategic attention.

The article defines architecture as an abstract framework that organizes business logic and algorithms, emphasizing abstraction, classification, and performance optimization across CPU, memory, I/O, and network.

Key capabilities for architects include strategic decomposition, abstraction (deduplication and reuse), classification (service modularization), and algorithmic performance improvements.

Examples of architectural patterns are presented: MySQL sharding and templating for data partitioning, CDN for network acceleration, service‑oriented design, and message queues for asynchronous decoupling.

The Weibo architecture is examined in three layers—client (web, Android, iOS), interface, and backend—highlighting security isolation, traffic control, and service segmentation (platform, search, big data).

Scaling challenges such as handling billions of page views, millions of QPS, and petabyte‑scale data are discussed, along with SLA requirements (four 9s availability, sub‑150 ms response).

Design principles include RPC services, messaging middleware, configuration management, stateless interfaces, careful data‑layer design, and mapping physical teams to logical architecture.

Multi‑level caching strategies are detailed: L1 local cache for QPS and bandwidth scaling, L2 distributed cache for capacity, and hybrid local + distributed cache for burst traffic.

The feed storage architecture uses sharding by user ID and time, separating hot and cold data, and employing two‑level indexing for efficient retrieval.

Distributed tracing is introduced to link logs across services using a unique request ID, enabling full‑chain monitoring with minimal intrusion via AOP or similar techniques.

Operational practices for handling traffic spikes include degradation plans, full‑chain load testing, and shared Docker clusters for resource efficiency.

Finally, the author recommends continuous learning—mastering Java, JVM, operating systems, design patterns, TCP/IP, distributed systems, and algorithms—to build a personal architecture design methodology.