moonming commented on PR #12128: URL: https://github.com/apache/apisix/pull/12128#issuecomment-4064881894
Hi @vahidaghazadeh, thank you for working on this proxy-chain feature! After careful consideration, I believe this functionality falls outside the scope of what an API gateway should handle: 1. **Architectural concern**: Chaining multiple upstream calls (proxy-chain pattern) is typically a service orchestration responsibility, better handled by a BFF (Backend For Frontend) layer, a service mesh sidecar, or an orchestration service rather than at the gateway layer. 2. **Complexity challenges**: Proper implementation would need robust error handling, timeout management, partial failure recovery, and response aggregation — which significantly increases complexity at the gateway layer. 3. **APISIX's design philosophy**: APISIX focuses on being a high-performance, low-latency gateway. Adding synchronous multi-hop proxying could significantly impact request latency and resource consumption. I'd recommend implementing this pattern at the application/service layer instead. If you have a specific use case that requires gateway-level orchestration, I'd love to hear more about it — perhaps we can find a better-fitting approach within APISIX's architecture. I'm going to close this PR, but please feel free to open a discussion issue if you'd like to explore alternatives. Thank you for your interest in APISIX! 🙏 -- 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]
