Evolution of Taobao Backend Architecture from Single Machine to Cloud‑Native High Concurrency

Before diving into the architecture, the article introduces basic concepts such as distributed systems, high availability, clustering, load balancing, and forward/reverse proxying.

Architecture Evolution

1. Single‑machine architecture : Tomcat and the database run on the same server; as traffic grows, resource contention appears.

2. First evolution – separate Tomcat and database : each component gets its own server, improving performance but making the database a new bottleneck.

3. Second evolution – local and distributed caching : introduce memcached (local) and Redis (distributed) to offload most read traffic from the database.

4. Third evolution – reverse‑proxy load balancing : deploy multiple Tomcat instances behind Nginx or HAProxy, dramatically increasing request capacity.

5. Fourth evolution – database read/write separation : use MyCAT to split reads and writes, allowing multiple read replicas.

6. Fifth evolution – business‑level sharding : allocate different databases per business to reduce contention.

7. Sixth evolution – table splitting (horizontal partitioning) : hash‑based or time‑based table splits enable massive horizontal scaling; MyCAT and MPP databases (Greenplum, TiDB, etc.) are mentioned.

8. Seventh evolution – LVS/F5 layer‑4 load balancing : use LVS or hardware F5 to balance traffic among multiple Nginx instances, with keepalived for high availability.

9. Eighth evolution – DNS round‑robin across data centers : configure multiple IPs for a domain to distribute traffic geographically.

10. Ninth evolution – NoSQL and search engines : introduce HDFS, HBase, Redis, ElasticSearch, Kylin, Druid, etc., to handle massive data and analytical workloads.

11. Tenth evolution – split monolith into smaller applications : isolate business domains, use ZooKeeper for distributed configuration.

12. Eleventh evolution – extract reusable functions as microservices : user, order, payment, auth services; managed via Dubbo or Spring Cloud.

13. Twelfth evolution – Enterprise Service Bus (ESB) : unify protocol conversion and reduce coupling, forming a SOA style architecture.

14. Thirteenth evolution – containerization : Docker images orchestrated by Kubernetes enable rapid deployment and scaling.

15. Fourteenth evolution – cloud platform adoption : move to public‑cloud IaaS/PaaS/SaaS, leveraging elastic resources, managed services, and big‑data stacks.

The article concludes with a set of architectural design principles such as N+1 redundancy, rollback capability, feature toggles, monitoring, multi‑active data centers, mature technology adoption, resource isolation, horizontal scalability, purchasing non‑core components, commercial hardware, rapid iteration, and stateless service design.

Author: Shi Hua, experienced in big‑data development and high‑concurrency distributed systems.