The article analyzes why manual capacity adjustments break down at ten‑million‑QPS scale, then walks through metric‑driven autoscaling, anti‑flapping algorithms, headroom planning, predictive scaling, stateful service challenges, and multi‑dimensional strategies to achieve a cost‑stable dynamic balance.
The ACM FSE‑2026 industry paper introduces a replication‑free failover mechanism for cloud‑native stateful services like Apache RocketMQ, using protocol‑level write isolation and multi‑attach storage to achieve second‑level recovery without extra data copies, while maintaining low cost and near‑native throughput.
This article details Kuaishou's migration of massive Redis clusters to Kubernetes using the KubeBlocks Operator, covering architecture, multi‑layer management requirements, federated cluster deployment, custom controllers, performance and stability considerations, and the resulting operational benefits.
Drawing on Kuaishou’s experience, this article examines whether stateful services like Redis belong on Kubernetes, outlines the benefits and risks, and details a cloud‑native solution using custom workloads, KubeBlocks, and a federated cluster architecture to achieve scalable, reliable Redis deployments.
This article explores the fundamentals of distributed systems, compares stateful and stateless services, examines monolithic, SOA, and microservice models, and provides practical guidance on access layers, fault tolerance, service discovery, scaling, and data storage for building robust cloud‑native architectures.
This article analyzes the motivations, models, and design considerations for building stateful distributed architectures—covering microservices, service discovery, access‑layer isolation, fault tolerance, scaling, and deployment strategies—to help architects create reliable, low‑latency cloud‑native systems.
This article examines the challenges and benefits of running stateful services such as Redis on Kubernetes, presents Kuaishou’s practical experience with cloud‑native migration, evaluates risks and performance impacts, and details the custom workloads, operators, federation and KubeBlocks solutions that enable large‑scale, reliable stateful service orchestration.
The article explains why many game server architectures resist adopting microservices, highlighting the critical need for ultra‑low latency, stateful communication, and high‑performance networking that microservice overhead and stateless designs can jeopardize.
Tencent Cloud TDMQ for Apache Pulsar achieves multi‑AZ high availability by containerizing ZooKeeper, BookKeeper and Brokers, using managed ZK, persistent cloud disks and elastic NICs, enforcing quorum and rack‑aware replicas, and planning cross‑region bidirectional replication to ensure seamless disaster recovery and continuous messaging.
This article details Bilibili’s journey of containerizing Elasticsearch and ClickHouse on Kubernetes, covering the challenges of stateful services, architectural decisions, custom operators, storage and network solutions, deployment steps, observability enhancements, and the resulting cost, quality, and efficiency gains.
This article explores various high‑availability strategies for stateful backend services, comparing cold backup, active/standby, same‑city active‑active, and multi‑site active‑active solutions, discussing their benefits, limitations, and practical implementation examples from large‑scale internet companies.
This article examines high‑availability strategies for stateful backend services, comparing cold backup, hot standby, same‑city active‑active, cross‑region active‑active, and multi‑active architectures, highlighting their advantages, limitations, and practical implementation considerations such as downtime, data loss, synchronization overhead, and conflict resolution.
eBay’s data infrastructure engineers describe how they design and implement cloud‑native, multi‑cluster high‑availability architectures for stateful data components—covering background challenges, federated Kubernetes management, state handling, fault‑tolerance, backup, and chaos testing—to ensure reliable, scalable data services across global data centers.
This article details New Oriental's approach to building stateful services on Kubernetes, covering the challenges of native storage, the use of custom Operators, the design of the XLSS local storage solution, backup and disaster‑recovery workflows, and a multi‑phase roadmap for large‑scale stateful middleware deployment.
This article examines the difficulties of running stateful services such as Redis, etcd, and MySQL on Kubernetes and presents practical solutions—including workload selection, CRD/operator extensions, scheduling strategies, high‑availability mechanisms, performance‑optimized networking and storage, and chaos‑engineering validation—to achieve reliable, high‑performance containerized deployments.
This article examines stateful backend services and compares various high‑availability strategies—including cold backup, dual‑machine hot standby, same‑city and cross‑city active‑active, and multi‑active architectures—highlighting their benefits, drawbacks, and practical implementation considerations.
This article explains how Facebook’s Twine system orchestrates containers across millions of servers, detailing its architecture, support for stateful services, cross‑data‑center control, elastic capacity handling, and the lessons learned from eight years of large‑scale operations.
The article analyzes why many game server architectures avoid microservices, highlighting real‑time latency requirements, stateful processing, network overhead, and the mismatch between typical microservice patterns and the high‑performance demands of multiplayer online battle arena games.
This article analyzes the evolution of high‑availability deployment—from cold backup to cross‑region multi‑active—explaining the trade‑offs of each solution, the challenges of stateful services, and real‑world architectures used by companies like Alibaba and Eleme.
This article examines stateful backend services and various high‑availability strategies—including cold backup, active/standby hot backup, same‑city active‑active, cross‑region active‑active, and multi‑active architectures—detailing their advantages, limitations, and practical implementation considerations, and includes real‑world examples from major e‑commerce platforms.
PouchContainer introduces an upgrade API that allows seamless, in‑place upgrades of stateful containers by preserving network, storage, and configuration while reducing API calls, offering consistency, flexibility, and robustness for enterprise‑scale deployments.
The article analyzes how the rapid adoption of microservices and container virtualization, especially Docker, boosts software agility and adaptability, while highlighting the critical role of stateful services, the challenges of storage in containers, and the concrete benefits of running both stateless and stateful components within containers.
