Use Edge Microgateway to protect intranet traffic while protecting internet traffic with Apigee Edge, deployment diagram is little confusing. Please help me understand same.
Above diagram says, Traffic hits Target API through intranet & again → Edge Micro → Target API . Why does it hit target API twice ?
Should it be like the below one ?
Is my understanding wrong ? Any help @docs @Prabhat Jha ?
Hi @Anil Sagar – Thanks for pointing this out. I’m trying to get clarification on the diagram and will post an update or revision as soon as it’s ready.
Target API Implementation on left is different from one of on the right. I can see why it’s confusing though. To give a more concrete example, Edge cloud proxies say is /orders which hits target API https://mycompany.com/orders (Target API Implementation on left ) which then would need to call multiple microservices (Target API implementation on right) internally say /customers and /transactions
Thank you @prabhat for the clarification. It’s helpful. @docs / @wwitman, Can we update this information / point to this post from @docs to avoid confusion ? Thank you.
Thanks @Anil Sagar – I added this information to the doc.
Awesome, Thank you @wwitman , +1ed your comment for sharing the update 
So what is stopping /orders calling /customers or /transactions directly without going thru Microgateway?
