Downloaded 35 times
Uploaded byJanani Velmurugan
02 api gateway
This document discusses API gateways as a solution for challenges that arise in microservices architectures. It describes how a monolithic architecture can become complex as services grow quickly. In a microservices architecture, clients could communicate directly with each service but this introduces problems around endpoint management, multiple requests, and refactoring difficulties. An API gateway provides a single entry point, routes requests to appropriate services, and aggregates results to address these issues. It then demonstrates Netflix Zuul, an open source API gateway, and provides a demo of its use with Eureka service discovery and routing between hello and goodbye microservices.
More Related Content
02 api gateway
- 1.
- 2. Agenda Monolithic Architecture Microservices Architecture Challenges & Limitations Solution – API Gateway Netflix Zuul Demo
- 3. Scenario Core servicesgrow very quickly as well as whole system complexity Hundreds of services involved in rendering of one complex webpage Ex: Amazon
- 4. Monolithic Architecture Amobile client retrieves this data by making a single REST call to the application, such as: GET api.company.com/productdetails/productId A load balancer routes the request to one of several identical application instances. The application then queries various database tables and return the response to the client
- 5. Microservices Architecture Datadisplayed on the product details page is owned by multiple microservices Shopping Cart Service – Number of items in the shopping cart Order Service – Order history Catalog Service – Basic product information such as product name, image, and price Review Service – Customer reviews Inventory Service – Low inventory warning Shipping Service – Shipping options, deadlines, and costs, drawn separately from the shipping provider’s API Recommendation Service(s) – Suggested items
- 6. Direct Client-to-Microservice Communication Clientcould make requests to each of the microservices directly Each microservice would have a public endpoint: https://serviceName.api.company.name This URL would map to the microservice’s load balancer, which distributes requests across the available instances. To retrieve the product-specific page information, the mobile client would make requests to each of the services listed in the previous slide
- 7. Challenges & Limitations Necessity to know all endpoints addresses The client in this example has to make seven separate requests Makes the client code much more complex Perform http request for each piece of information separately Merge the result on a client side Difficult to refactor the microservices Non web-friendly protocols
- 8. Solution – APIGateway
- 9. API Gateway Asingle entry point into the system Handle requests by routing them to the appropriate backend service or by invoking multiple backend services Aggregating the results
- 10. API Gateway –Usage
- 11. API Gateway -Usage Request routing Composition Protocol translation
- 12. Netflix Zuul Project Zuul is a gateway service that provides dynamic routing, monitoring, resiliency, security and more. Zuul = Spring Cloud + Netflix
- 13.
- 14.
- 15. Demo – Hello/GoodbyeService NOTE: To create GoodbyeService, Replace hello with goobye and server.port=2222
- 16.
- 17.
- 18.
- 19. Zuul Filters -Types
- 20. Thank You https://github.com/JananiVelmurugan discovery-server gateway-service hello-service goodbye-service