This article introduces Sentinel, a cloud‑native flow‑control component born from Alibaba's ecosystem, explains its resource‑based rule model, core implementation—including rule‑control chain, datasource, and dashboard—and discusses practical deployment considerations and extension strategies for Java microservices.
This article revisits Sentinel, Alibaba’s open‑source traffic‑governance component, explaining its core concepts, resource and rule definitions, step‑by‑step demos for basic and Spring integration, and a detailed walkthrough of its internal processor slots, statistics nodes, flow control, and degradation mechanisms.
This article explains how to achieve high‑availability in microservice systems through traffic governance techniques such as circuit breakers, various isolation strategies, retry mechanisms, timeout controls, and rate‑limiting, illustrating each concept with examples, formulas, and pseudo‑code.
The article explains how traffic governance—including circuit breaking, isolation, retries, degradation, timeout handling, and rate limiting—maintains the three‑high goals of high performance, high availability, and easy scalability in microservice architectures, using practical examples and formulas.
This article explains how traffic governance—including circuit breaking, isolation, retry mechanisms, degradation, timeout control, and rate limiting—helps microservice systems achieve the three‑high goals of high performance, high availability, and easy scalability, using concrete formulas, algorithms, and practical examples.
This article explains how traffic governance—through circuit breaking, isolation, retry strategies, degradation, timeout handling, and rate limiting—keeps distributed systems highly available, performant, and scalable, using concrete examples, formulas, and best‑practice patterns for modern microservice architectures.
This article explains how traffic governance—including circuit breaking, isolation, retry, downgrade, timeout, and rate‑limiting—keeps microservice architectures highly available, performant, and easy to scale by balancing load, preventing cascading failures, and optimizing resource usage.
Alibaba Sentinel 1.8.7 introduces regex‑based resource matching, Prometheus metric export, default circuit‑breaker rules, and an enhanced RateLimitController, while outlining the upcoming 2.0 features such as traffic routing, traffic coloring, and self‑healing capabilities for cloud‑native microservices.
This article explains how to achieve the three‑high goals of high performance, high availability and easy scalability in microservice systems by using traffic governance techniques such as circuit breaking, various isolation strategies, retry mechanisms, timeout controls, degradation tactics and rate‑limiting, illustrated with practical examples and diagrams.
The article details Bosideng’s multi‑year digital transformation, describing how the apparel company migrated its legacy systems to cloud‑native architectures using Kubernetes, containerization, unified microservices, and Alibaba Cloud MSE to achieve zero‑loss deployment, traffic governance, and accelerated business innovation.
This article introduces an online practice of cluster rate limiting based on Sentinel, providing a high-availability solution for Sentinel cluster rate limiting and implementing automatic allocation and failover of Token servers.
Effective traffic governance and protection rely on properly configuring thresholds—either a fixed global limit that stays constant regardless of node count, or a per‑machine allocation that scales the total capacity as nodes are added or removed—to prevent sudden surges from overwhelming services and ensure high availability.
