The article reviews the Spring Cloud Hoxton release, detailing version upgrades across the Spring ecosystem, introducing a new load‑balancer implementation, a unified circuit‑breaker API, expanded reactive support, and a comprehensive list of updated components for developers transitioning to Spring Boot 2.2.x.
This article explains what an API gateway is, why it’s crucial for microservice architectures, outlines its core functions such as authentication, load balancing, traffic control, and logging, describes its typical three‑layer architecture, dives into technical principles like protocol conversion and asynchronous processing, and compares popular open‑source gateways such as Kong, Traefik, Ambassador, and Zuul.
This article provides a comprehensive tutorial on using Hystrix for circuit breaking in Spring Cloud microservices, covering theory, isolation strategies, detailed YAML configuration, fallback implementation, dynamic updates with Archaius, timeout settings across Feign, Ribbon, and HttpClient, as well as dashboard visualization and all related property groups.
This article explores best‑practice patterns for microservice communication, covering synchronous and asynchronous protocols, serialization formats, API design, service discovery, versioning, rate limiting, circuit breakers, correlation IDs, distributed consistency, authentication, retries, and economic considerations.
This article explains the concept of circuit breaking and rate limiting in micro‑service architectures, compares Hystrix and Istio implementations, details Istio's ConnectionPool and outlierDetection settings, maps their parameters to Envoy, and provides step‑by‑step command‑line examples that demonstrate how these controls behave in practice.
This article outlines eight practical high‑availability techniques—multiple replicas, isolation, rate limiting, circuit breaking, degradation, gray releases with rollback, comprehensive monitoring, and proactive log alerting—to help engineers design systems that are both efficient and reliable under heavy load.
This article explains a practical circuit‑breaker design for backend services, detailing detection logic, algorithm thresholds, time‑window statistics, recovery duration, manual overrides, a global switch, and how to monitor the breaker’s current state using Redis.
This article explains a project's circuit breaker implementation, covering detection steps, the algorithm based on request count and failure rate, time‑window statistics, recovery duration, manual activation, a global enable switch, and how to monitor its current state.
The article explains why interface-level failures occur, distinguishes internal and external causes, and presents four practical strategies—degradation, circuit breaking, rate limiting, and queuing—to keep core services running and protect most users under heavy load.
This article explains why Hystrix is needed for handling unstable third‑party HTTP services, demonstrates both annotation‑based and command‑style integrations with code examples, shows how to configure thread pools, semaphores, fallback methods, dynamic properties, and circuit‑breaker thresholds, and provides a summary of best practices for resilient backend development.
This article explains why Hystrix is essential for large distributed systems, describes its dependency isolation mechanisms—including command, group, thread‑pool, and semaphore isolation—covers circuit‑breaker behavior, fallback strategies, and provides detailed Java code examples for configuration and usage.
The article explains why service rate limiting is essential in distributed systems, describes common design patterns such as circuit breaking, service degradation, delayed processing, and privilege handling, and outlines practical techniques like circuit‑breaker libraries, counters, queues, and token‑bucket algorithms while highlighting key operational considerations.
This article clarifies the differences between service degradation and circuit breaking, explains how service avalanches occur, and provides practical Spring Cloud and Hystrix configurations along with code examples to implement resilient microservice architectures.
This article introduces Spring Cloud as a Spring Boot‑based microservice framework, explains the fundamentals of service architecture through a relatable story, details essential components such as service registry, load‑balanced calls, circuit breakers, gateways, configuration management, and provides concrete Java code examples for each part.
This article introduces a series of microservice design patterns—including database isolation, observability, and cross‑cutting concerns—explaining the underlying problems each pattern solves and providing concrete solutions such as CQRS, Saga, log aggregation, health checks, and blue‑green deployments.
This article explains the concept of circuit breaking in distributed systems, outlines a four‑step implementation process with strategies for detecting unhealthy services, cutting off calls, probing recovery, and restoring normal operation, and shares best‑practice tips to minimize downtime and improve resilience.
With Hystrix no longer receiving new features, this article explains how developers can smoothly transition to Alibaba’s Sentinel by comparing the two libraries, detailing command migration, thread‑pool vs semaphore isolation, circuit‑breaker configurations, annotation support, and dynamic rule management for robust microservice resilience.
This article walks through a typical e‑commerce order‑payment scenario to illustrate how Spring Cloud’s core components—Eureka for service discovery, Feign for declarative HTTP clients, Ribbon for client‑side load balancing, Hystrix for fault isolation and circuit breaking, and Zuul as an API gateway—collaborate to build resilient microservices.
This article explains the principles and operation of circuit breakers and retry mechanisms in microservice architectures, describes their three states, key configuration parameters, demonstrates a Hystrix‑Go implementation, and discusses back‑off strategies and the combined use of both techniques for resilient backend services.
The article explains the causes of service avalanche in distributed systems—especially cache avalanche—and presents comprehensive mitigation strategies such as diversified cache expiration, circuit‑breaker, isolation, and rate‑limiting techniques to keep applications resilient under load.
This article explains the role of circuit breakers in microservice architectures, introduces Netflix Hystrix and its integration with Spring Cloud, and provides detailed configuration, usage examples, and best‑practice guidelines for building resilient Java backend services.
This article outlines ten crucial design principles for building robust microservice systems, covering API gateways, stateless services, database scaling, caching, service splitting, orchestration, configuration management, logging, resilience patterns, and comprehensive monitoring to ensure high performance and reliability.
This article details Meituan's practical approaches to boosting account service reliability, covering MTBF/MTTR metrics, business‑level monitoring, flexible availability with circuit‑breaker patterns, cross‑region active‑active deployment, data synchronization techniques, and the measurable performance gains achieved.
This article analyzes the rapid growth challenges of Meituan‑Dianping's core payment flow, explains key availability metrics such as MTBF and MTTR, and presents a comprehensive set of architectural, operational, and tooling strategies—including dependency decoupling, timeout tuning, circuit breaking, and full‑link stress testing—to achieve stable, fault‑tolerant transactions.
This article explains the circuit breaker pattern for distributed systems, detailing its problem context, state machine solution, implementation in C#, key considerations, usage scenarios, and comprehensive unit tests, illustrating how to improve system resilience and prevent cascading failures.
Effective fault tolerance is crucial for microservice stability, and this article explores core design principles and classic patterns—such as timeout retries, rate limiting, bulkhead isolation, circuit breakers, and fallback strategies—guiding developers to choose and combine the right approaches for high‑availability systems.
This article details the implementation of a custom circuit breaker to prevent system failures in distributed systems, covering design principles, Java and Python implementations, and its effectiveness during high traffic periods.
This guide walks beginners through the fundamental components of microservice infrastructure—configuration management, service registry, API gateway, authentication, message broker, BFF, circuit breaker, and load balancing—explaining their roles, interactions, and practical considerations for building resilient systems.
This article explains what overload means in server development, analyzes a concrete proxy overload case, identifies root causes, and presents a multi‑layer protection strategy—including self‑protection, downstream safeguards, concurrency control, and improved circuit‑breaker designs—to keep services stable under heavy traffic.
This article explains microservice fault‑tolerance techniques—including timeout settings, retry strategies, circuit‑breaker logic, current limiting, resource isolation, and service degradation—from both micro and macro perspectives, illustrating how to design resilient service chains and avoid cascading failures.
The article explains how Meituan‑Dianping applies classic fault‑tolerance patterns—timeout and retry, rate limiting/load shedding, circuit breaker, bulkhead isolation, and fallback—to design for failure, prevent cascading service outages, and enhance system stability and high‑availability in a service‑oriented architecture.
This article explains five stability patterns—retry, timeout, circuit breaker, handshaking, and bulkhead—used to keep distributed systems resilient, illustrates their implementation with JAX‑RS/RESTful services in Java, and shows how asynchronous Java 8 techniques further improve reliability.
