Over ten years of BAT architecture experience, shared generously!
The article explains Nginx's caching mechanism, showing how storing backend responses in memory or disk and designing proper cache keys can dramatically reduce backend load and latency, delivering performance improvements of several times to over tenfold.
The article explains that achieving stable performance for Spring Cloud Gateway at a million‑request scale requires a reactive non‑blocking model, comprehensive rate‑limiting and circuit‑breaker mechanisms, and optimized connection management and routing to handle high concurrency efficiently.
The article explains how Nginx’s event‑driven, asynchronous non‑blocking model, master‑worker multi‑process design, efficient I/O multiplexing (epoll/kqueue), and lightweight resource‑control architecture enable it to sustain extremely high concurrency with minimal overhead.
The article reviews four major distributed storage systems—HDFS, Ceph, GlusterFS, and FastDFS—detailing their architectures, core strengths such as HDFS’s batch processing, Ceph’s unified object/block/file capabilities, GlusterFS’s horizontal scalability, and FastDFS’s lightweight handling of small files, while also noting each solution’s limitations.
The article walks through a step‑by‑step Nginx performance tuning guide, covering worker_processes and worker_connections settings, Linux file‑descriptor limits, sysctl tweaks such as net.core.somaxconn and tcp_max_syn_backlog, explicit listen backlog, and zero‑copy sendfile with tcp_nopush/tcp_nodelay to dramatically increase throughput and lower CPU usage.
Alibaba’s same‑city active‑active architecture deploys multiple data centers within one city, splits traffic between them, and ensures instant failover with layered high‑availability across access, application, and data layers, using technologies like DNS, SLB, Nginx, Redis and OceanBase.
MySQL’s concurrency capacity isn’t a single number; it’s measured by QPS and TPS and varies with query complexity, indexing, transaction design, and hardware, with simple indexed reads reaching several thousand QPS on a well‑tuned server, while mixed or complex workloads often cap around one to two thousand QPS.
The article explains Alibaba’s “two‑region three‑center” architecture, detailing how geographically separated primary, backup, and disaster‑recovery data centers work together to provide financial‑grade high availability and protect against single‑site failures or regional catastrophes.
The article explains how to build a million‑request‑per‑second system by combining LVS, Nginx, and Keepalived in a three‑layer load‑balancing architecture, detailing each layer’s responsibilities, configuration snippets, and kernel tuning parameters that ensure high throughput and seamless failover.
The article breaks down Alibaba’s same‑city active‑active high‑availability architecture, detailing its four design layers—traffic scheduling, stateless application services, data replication, and operational automation—while illustrating how each component ensures continuous service during data‑center failures.
