kayx23 commented on code in PR #2130: URL: https://github.com/apache/apisix-website/pull/2130#discussion_r4118864024
########## website/learning-center/api-gateway-for-microservices.md: ########## @@ -97,15 +97,15 @@ Not always. If the mesh ingress already provides the external routing and policy ### How does an API gateway handle partial failures across microservices? -An API gateway can be configured with circuit breakers, timeouts, and retry policies for each upstream service. When using the API composition pattern, the gateway can return partial results with degraded status rather than failing the entire request when one backend is unavailable. APISIX supports configurable timeouts and retry counts per route, and health checks automatically remove unhealthy nodes from the upstream pool. +An API gateway can apply timeouts, bounded retries, circuit-breaking policies, and configured health checks before or while routing to an upstream. Those controls can contain some failures, but they do not define how a composed business response should degrade. If a client operation combines several services, place partial-result and fallback policy in the composition layer and specify which missing results are acceptable. In APISIX, health checks exclude nodes only after the configured active or passive thresholds mark them unhealthy; if no healthy node is available, the documented fallback behavior must also be included in the failure design. Review Comment: Before deleting the overlapping blog, please preserve or explicitly account for its unique reader guidance. The surviving landing now covers the service-mesh alternative, but it still omits the old article’s broader "when you may not need a gateway" criteria (simple/internal systems, existing ingress or load balancer, operational readiness), its gateway-versus-service responsibility matrix, the single-gateway failure-domain and unbounded-plugin risks, and its practical evaluation checklist. Those are substantive decision and operations content, not duplicate wording. Migrate the useful points into the landing (or document why each is intentionally out of scope) before consolidating both historical URLs onto it. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
