We're deploying a GraphQL service written in NodeJS in Apigee.
What is the best practice on reaching target endpoints?
Is it okay for my GraphQL services to reach target endpoints via Apigee proxy services?
or since I'm calling within the context of a NodeJS proxy, I'm better off calling the end point directly?
I'd prefer to call into Apigee endpoints.
Solved! Go to Solution.
In Apigee, a Node JS application is a Target in itself. As such, the typical pattern is to call the endpoints directly. Any traffic management, caching, analytics and security policies can be added to the Request and Response flows of the proxy. This means they will be executed before or after the Node JS application. In my experience this is usually sufficient.
If you have a specific use-case that you think requires something different, please provide more detail so we can discuss. In the worst case scenario you can call back into Edge from Node JS, but this adds unnecessary latency.