Member-only story
API Gateway in Microservices
In this article, we will get to know one of the key patterns in microservices architecture — API Gateway. It covers the needs, implementation, technologies and challenges associated with it.
Overview
Microservices expose the fine-grained APIs to the client APIs. When the user interfaces interact with the services directly, the communication usually becomes — chatty, which needs multiple calls to render a single view on the client side.
Let’s assume we have an e-commerce system based on microservices architecture. We have different microservices including Product Catalog, Product Recommendations, Product Reviews, etc. If we have to render a product view, which includes the details related to product, reviews and recommendations, we need to call Product Catalog, Product Reviews and Product Recommendation services separately.
In the real world e-commerce sites, product details view carries much more information and needs to make many more calls to render the page. In fact amazon claims that close to hundred services are involved in rendering its product details view.
