Evolution of Taobao Backend Architecture: From Single‑Server Deployment to Cloud‑Native Microservices

The article begins by defining fundamental concepts such as distributed systems, high availability, clusters, load balancing, and the differences between forward and reverse proxies.

It then walks through thirteen evolutionary stages of Taobao's backend architecture:

Stage 1: Separate Tomcat and database onto different servers.

Stage 2: Add local and distributed caches (memcached, Redis) to reduce database load.

Stage 3: Deploy multiple Tomcat instances behind a reverse‑proxy (Nginx/HAProxy) for load balancing.

Stage 4: Implement database read/write separation using middleware like Mycat.

Stage 5: Split databases by business domain to reduce contention.

Stage 6: Partition large tables into smaller shards based on hash or time.

Stage 7: Use LVS or hardware load balancers (F5) to balance traffic among Nginx nodes.

Stage 8: Apply DNS round‑robin for inter‑datacenter load distribution.

Stage 9: Introduce NoSQL stores and search engines (e.g., Elasticsearch, HBase) for analytics and full‑text search.

Stage 10: Break a monolithic application into smaller, independently deployable services.

Stage 11: Extract common functionalities into microservices (using Dubbo, Spring Cloud).

Stage 12: Adopt an Enterprise Service Bus (ESB) to unify service interfaces.

Stage 13: Containerize services with Docker and orchestrate them with Kubernetes.

Afterward, the article discusses cloud adoption (IaaS, PaaS, SaaS) to provide elastic resources and simplify operations.

Finally, it summarizes architectural design principles such as N+1 redundancy, rollback capability, feature toggles, monitoring, multi‑active data centers, mature technology selection, resource isolation, horizontal scalability, purchasing non‑core components, using commercial hardware, rapid iteration, and stateless design.