policy mashup - latency

Google Cloud Apigee
1

I read from the documentation on apigee site (api proxy cookbook) - for javascript policy mashup

“One use for a pattern like this is to create a mashup of data pulled from multiple backend services. At the same time, because the JavaScript is attached to the API proxy as a policy, it can participate in Apigee Edge features like traffic management, security, mediation, and analytics”

Does this mean it will be routed to the Apigee gateway for each of the backend calls? does this introduce any latency? (I understand that policies are executed in the message processor component.)

2

The Service Callouts to each of the different backends do not go through the Apigee gateway. The performance for the different API calls should be comparable to calling it directly. We have a number of high traffic customers who use this feature heavily and don’t have any problems with performance.