Tagged articles
fallback
28 articles · Page 1 of 1
This article explains why AI Gateways are increasingly adopted, detailing their core functions—protocol normalization, model routing, key management, and observability—with a practical LiteLLM implementation guide, plus pros, cons, and ideal use cases for multi-model, cost-sensitive, and enterprise environments.
AI gatewayLiteLLMObservability
0 likes · 19 min read

The article details a CI lint failure caused by a corrupted Go module from a GOPROXY mirror, revealing that comma-separated GOPROXY fallbacks only retry on 404/410 errors, while pipe-separated fallbacks retry on any error—a behavior confirmed by Go source code analysis.
CI debuggingGOPROXYGo modules
0 likes · 14 min read

This article details a complete microservices high-availability system using Sentinel, covering dual-layer rate limiting, circuit breaking with three states, active degradation strategies, and fallback methods to prevent cascade failures during traffic spikes and downstream failures.
Cascade FailureHigh AvailabilitySentinel
0 likes · 16 min read

Hermes Agent’s auxiliary_client.py implements a seven‑level provider fallback chain that ensures auxiliary tasks keep running even if the main LLM crashes, runs out of credits, or hits rate limits, by prioritizing the user’s primary provider, cycling through alternative providers, and handling protocol quirks.
AI agentsHermesLLM
0 likes · 14 min read

The article classifies agent failures into transient, structural, and semantic types, compares how Claude Code, OpenAI Codex, and Google Gemini CLI agents handle errors, and shows how LangGraph implements robust retry policies, fallback routing, and human‑in‑the‑loop handoff with concrete code examples and best‑practice guidelines.
AgentLangGraphRetry
0 likes · 16 min read

This article outlines a production‑grade LLM Gateway design, detailing a three‑layer architecture, capability‑, cost‑, latency‑ and semantic‑based routing strategies, multi‑level fallback mechanisms, specialized load balancing, unified API adaptation, semantic caching, observability, and compares popular open‑source implementations.
GatewayLLMObservability
0 likes · 17 min read

The article outlines a production‑grade LLM Gateway architecture divided into ingress, decision, and egress layers, detailing capability‑based, cost‑aware, latency‑aware, and semantic routing, multi‑stage fallback mechanisms, specialized load‑balancing, protocol unification, semantic caching, observability, and evaluates open‑source solutions such as LiteLLM, RouteLLM, and Portkey.
LLM GatewayObservabilityRouting
0 likes · 18 min read

This article compares RestTemplate and OpenFeign for inter‑service calls, demonstrates how to set up OpenFeign with Spring Cloud, covers advanced configurations such as timeouts, retries, interceptors, logging, fallbacks, and circuit breaking, explains load‑balancing strategies, shares a complete microservice implementation, and resolves common pitfalls.
Feign ClientOpenFeignRetry
0 likes · 13 min read

This guide explains how Alibaba Cloud AI Gateway provides traffic management, passive health checks, first‑packet timeout, and fallback mechanisms to keep large language model services highly available during traffic spikes and overload scenarios.
First Packet TimeoutLLMPassive Health Check
0 likes · 8 min read

An engineer recounts a midnight outage caused by misconfigured timeouts in Feign, Ribbon, and Hystrix, explains three common pitfalls, and presents a four‑step strategy—clarifying configuration hierarchy, intelligent retry, user‑friendly fallback, and dynamic Sentinel circuit breaking—to boost system availability from 91% to 99.97%.
Circuit BreakerRetrySpring Cloud
0 likes · 9 min read

This tutorial walks through deploying vLLM inference services on a GPU‑enabled Kubernetes cluster using llmaz, configuring Higress as an AI gateway for traffic control, observability, and fallback model switching, and demonstrates end‑to‑end request testing.
HigressObservabilityfallback
0 likes · 15 min read

Explore how to construct robust, multi‑layered fallback mechanisms in Rust’s Axum framework—covering basic route guards, global error handling, middleware validation, dynamic redirects, performance optimizations, and monitoring—so every unknown HTTP request is safely captured, logged, and intelligently responded.
AxumRustWeb
0 likes · 10 min read

This article explains the new @Fallback annotation introduced in Spring 6.2, compares it with @Primary, shows code examples of bean configuration, and details the bean selection order changes before and after the 6.2 release.
@BeanPrimarydependency-injection
0 likes · 5 min read

This article explains why a copy button failed on mobile browsers, compares the modern Clipboard API with the deprecated document.execCommand method, and provides a robust fallback implementation in a custom React hook that works across browsers and secure contexts.
COPYclipboardfallback
0 likes · 5 min read

This article explains the concept of service degradation, defines SLA levels, and details various degradation techniques—including fallback data, rate‑limiting, timeout handling, circuit‑breaker retries, and front‑end/ back‑end strategies—to maintain high availability during traffic spikes or component failures.
Circuit BreakerSLAfallback
0 likes · 13 min read

This article explains software resilience concepts, introduces the four latency‑control patterns—retry, fallback, timeout, and circuit breaker—illustrates them with a payment‑fraud‑check example, and shows how to implement them in Vert.x using Kotlin code.
KotlinRetryTimeout
0 likes · 14 min read

Service degradation, a crucial reliability technique, involves selectively disabling non-essential features, applying rate limiting, timeout handling, fallback data, and tiered switches across front‑end, back‑end, and infrastructure layers to maintain core functionality during traffic spikes or component failures, ensuring high availability and meeting SLA targets.
OperationsSLAfallback
0 likes · 13 min read

The article explains service degradation concepts, defines SLA levels and the meaning of six nines, and details various degradation techniques such as fallback data, rate‑limiting, timeout, fault handling, read/write strategies, frontend safeguards, and the use of switches and pre‑embedding to maintain system availability during traffic spikes or failures.
Circuit BreakerOperationsSLA
0 likes · 12 min read

This article explains the concept of service degradation, defines SLA levels including the six‑nine metric, and details practical strategies such as fallback data, rate‑limiting, timeout handling, read/write degradation, retry mechanisms, and front‑end techniques to maintain high availability during traffic spikes.
High AvailabilitySLAfallback
0 likes · 14 min read

This article explains the concept of service degradation, its relationship with rate limiting and SLA, and presents various practical mitigation techniques such as fallback data, rate‑limit throttling, timeout handling, fault isolation, retry mechanisms, feature switches, read/write degradation, and front‑end strategies to maintain high availability during traffic spikes or component failures.
Circuit BreakerHigh AvailabilitySLA
0 likes · 13 min read


ByteFESep 7, 2021 · Frontend Development
This article explains why setting font‑weight 500 on PingFangSC‑Regular produces the same visual result as 400, why some Android devices only bold numeric/English characters, and provides practical fallback strategies and code examples for reliable mobile font rendering.
CSSfallbackfont-family
0 likes · 13 min read

This article explains the concepts of service circuit breaking and degradation, introduces Hystrix and its design goals, and provides step‑by‑step code examples for integrating Hystrix, Feign, and Spring Cloud components to achieve resilient microservice communication with fallback handling.
FeignHystrixfallback
0 likes · 12 min read

When a CDN becomes inaccessible, a website's static resources can disappear, but by detecting failed CDN requests and automatically retrying them from the main domain—while preserving HTML, CSS, image, and especially JavaScript execution order—developers can ensure continuous site availability.
CDNfallbackfrontend
0 likes · 8 min read

This article explains Eureka's normal workflow, how it registers services, replicates data, and maintains local caches, and details its fallback mechanisms, unavailable server handling, full‑outage resilience, and self‑preservation feature to keep microservice discovery reliable.
EurekaHigh Availabilityfallback
0 likes · 5 min read

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.
Backend ResilienceCircuit BreakerDynamic Configuration
0 likes · 21 min read

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.
Circuit BreakerRetrybulkhead
0 likes · 14 min read


21CTONov 6, 2015 · Frontend Development
This article explains why large‑scale front‑end pages like Taobao’s homepage need reliable fallback mechanisms, outlines common failure scenarios, and presents practical strategies such as request retries, local caching, and backup APIs to keep the UI functional under high traffic and network issues.
API resilienceCachingfallback
0 likes · 9 min read

The article explains why high‑traffic web pages need robust fallback and disaster‑recovery mechanisms, outlines common failure scenarios, and presents practical solutions such as request retries, local caching, backup interfaces, and hard‑coded data with illustrative JavaScript code.
AJAXdisaster recoveryfallback
0 likes · 10 min read
