API Gateway Design

Multi tool use
Multi tool use
The name of the pictureThe name of the pictureThe name of the pictureClash Royale CLAN TAG#URR8PPP


API Gateway Design



Api gateway http://microservices.io/patterns/apigateway.html seems to be a good pattern to be adopted in Micro Service architecture(Not internal communication between services).



But I have below queries



I am unable to understand how API Gateways should be designed itself. We can't have just one api gateway for all services. For example for Uber we have
Trip, Cabs, Driver, User, Pricing Micro Services, so how many API Gateways should we design.



In https://medium.com/netflix-techblog/optimizing-the-netflix-api-5c9ac715cf19 what does Dynamic Endpoints means.



I was thinking like in Uber case,to display user first page we will need cabs and pricing. So we will expose an API in api-gateway some /home and from here asynchronously we will call Pricing and Cabs api will merge and return the response. Is there any batter way to do this?









By clicking "Post Your Answer", you acknowledge that you have read our updated terms of service, privacy policy and cookie policy, and that your continued use of the website is subject to these policies.

hRbmHhxA,go9cT0VteD7BuoN5JVs9E flQrRr3CEIc,f9LJ4pOBf,Kv5J2 5o,r,geXI27NWUxsnar08hs,gO,7bldxk
NsD4LSv48WtB5yPr Pm8RDD5sT 4N7B gfqo1,zLX1UDIYfCry0zt4TjbkK5koNvBKwqagD4CY,hH3xdTMaBO9n6,qIW0

Popular posts from this blog

Makefile test if variable is not empty

Visual Studio Code: How to configure includePath for better IntelliSense results

Will Oldham