0 views collected around this technical thread.
The article explains how elastic architecture, through auto‑scaling and failover mechanisms, dynamically adjusts resources and ensures continuous service during traffic spikes and component failures, improving cost efficiency, reliability, and operational stability for modern cloud‑based applications.
This article describes how the QMQ delay‑message service was refactored by separating business logic from storage, adopting Apache BookKeeper for high‑availability, zone‑aware disaster recovery, a configurable DNS resolver, a ZooKeeper‑based task coordinator, and a multi‑level sliding‑time‑bucket scheduler to achieve a stateless, elastic architecture.
The article details how Alipay engineers tackled the massive traffic spikes of Double 11 by addressing external payment bottlenecks, implementing recharge‑based balances, building capacity‑planning platforms, adopting logical data‑center (LDC) and CRG zone architectures, deploying elastic scaling, and evolving their OceanBase database and service‑mesh infrastructure to sustain millions of transactions per second.
This article details the evolution of JD's Elastic Database, describing the challenges of scaling MySQL, the staged solutions including sharding, JProxy, and the final elastic architecture with services like Topology, JED‑Gate, and JED‑Tablet, and explains its query processing, dynamic resharding, and automatic failover mechanisms.
The article summarizes Google’s recent papers that outline an architectural guide for creating elastic, scalable web applications on Google Cloud Platform, describing key components such as regions, zones, load balancers, autoscalers, Cloud SQL, Cloud Storage, and deployment best‑practices.