bzp2010 commented on issue #2498: URL: https://github.com/apache/apisix-ingress-controller/issues/2498#issuecomment-3248031059
I've reviewed this extension project, and it might be feasible for APISIX. However, I must point out that we face significant technical hurdles here. A particularly critical issue is that this extension requires the gateway data plane to implement the EPP client protocol. This protocol is based on ext-proc, an internal protocol incubated by Envoy that relies on gRPC bidirectional streams instead of standard HTTP requests/responses or WebSockets. Implementing a gRPC client on an OpenResty-based (essentially nginx) tech stack presents structural complexity. While nginx can proxy gRPC, it lacks a mechanism to autonomously generate gRPC requests internally. A request cannot originate and process itself; it must be initiated by an external client outside nginx. Numerous OpenResty-based API gateways exist, e.g., APISIX, Kong, and others. None offer native mechanisms for efficiently implementing gRPC clients (though some may use WASM workarounds, which are far from optimal). How should I summarize this reality? Discrimination brought by Envoy? A significant portion of the ecosystem's established technologies—far more historic and reputable than Envoy—are simply ignored. There's an arrogant assumption that all implementations must conform to this proprietary technology, forced into a “de facto standard” (which it most certainly is not), rather than any neutral, implementation-agnostic approach. This is truly regrettable. Perhaps we will have to implement an external component to address this, i.e., bridge ext-proc to standard HTTP. Perhaps you could offer alternative perspectives to inspire a different approach for integrating APISIX with this new ecosystem. I remain open to this and look forward to hearing from you. -- 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: notifications-unsubscr...@apisix.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
