Yilialinn commented on code in PR #2130: URL: https://github.com/apache/apisix-website/pull/2130#discussion_r4119372872
########## 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: Addressed in commit 39a58f2f7f7ac7d335ad311aae9134f6e556c1f9. The surviving Learning Center page now preserves the retired article guidance on when simpler alternatives are sufficient, gateway-versus-service responsibilities, gateway failure domains, gateway-only security and unbounded plugin risks, and a six-point APISIX evaluation checklist. I also updated the page description and linked the plugin guidance to the dedicated Plugin terminology page. Validation completed on the exact final tree 02311d6a9e8f141019df88445da8f8fda0fa80ed: frontmatter and content checks, 0 broken documentation links, sitemap/canonical and redirect/consolidation checks, a 896-page Astro build, desktop and 390px responsive inspection, and independent review with no content P0-P3 findings. All PR checks now pass, including the full Docusaurus/Astro build and final desktop/mobile browser tests. -- 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]
