Kubernetes v1.35, nicknamed “Timbernetes,” adds 60 enhancements—including in‑place vertical pod scaling, a new KYAML format, group scheduling for AI workloads, and deprecations such as Ingress NGINX—while delivering 17 stable, 19 beta, and 22 alpha features for production and testing.
This guide explains both the traditional restart‑based method and the modern InPlacePodVerticalScaling feature introduced in Kubernetes 1.27+, showing step‑by‑step commands, prerequisites, limitations, and best‑practice recommendations for safely performing vertical pod scaling in production environments.
This proposal introduces in‑place vertical scaling for Pods by making PodSpec resources mutable, extending PodStatus with ResourcesAllocated, adding ResizePolicy and Resize fields, and updating the CRI UpdateContainerResources and ContainerStatus APIs to support live CPU and memory adjustments without restarting containers.
This article explains how to design and evolve a system from a single‑server deployment to a highly scalable architecture using vertical and horizontal scaling, load balancing, database replication, sharding, caching, CDN, and stateless design to support billions of users.
This article explains the three aspects of database sharding—database‑only, table‑only, and both—detailing when to apply each, how to choose sharding keys, common algorithms, ID generation strategies, available open‑source tools, and the new challenges introduced by sharding.
The article explains how to build highly available stateless services by using redundant deployment, vertical and horizontal scaling, appropriate load‑balancing algorithms, monitoring, and automated recovery, and also discusses high‑concurrency identification, CDN/OSS usage, and practical recommendations for cloud‑native environments.
This article explains how to evolve a simple single‑server web application into a highly available, horizontally scalable system by introducing DNS routing, vertical and horizontal scaling, load‑balancing, database replication, sharding, denormalization, SQL/NoSQL choices, caching, CDN, and GeoDNS techniques.
This article explains how to achieve high availability for stateless services by employing redundancy, vertical and horizontal scaling, various load‑balancing algorithms (random, round‑robin, weighted, least‑connections, source‑hash), and automatic scaling techniques in cloud‑native environments, while also covering performance monitoring and CDN/OSS usage.
This article explains the fundamentals of database sharding, covering both vertical and horizontal partitioning concepts, routing algorithms, advantages and drawbacks, practical implementation steps using sharding-jdbc, and discusses related challenges such as distributed transactions, pagination, global IDs, and tool selection.
The QLive service powers iQIYI’s massive live‑streaming events—such as the Spring Festival Gala—by combining vertical and horizontal scaling, a three‑layer architecture with dual data‑center isolation, multi‑level caching, circuit‑breaker/degradation controls, and a Flume‑Kafka‑Hive monitoring pipeline to sustain over 400 k QPS and 99.9999 % availability.
This article explains why scalability is a crucial non‑functional requirement, describes vertical (scale‑up) and horizontal (scale‑out) approaches, introduces the AKF model’s X/Y/Z axes, and provides practical guidance for scaling services, databases, caching, and deployment to achieve robust, high‑throughput applications.
