API-GATEWAY-CLIENT-SIDE-LOAD-BALANCNG-IN-MICROSERVICES скачать в хорошем качестве

API-GATEWAY-CLIENT-SIDE-LOAD-BALANCNG-IN-MICROSERVICES

This video demonstrates how an API Gateway is used to perform client side load balancing. You will have a client such as Postman, a mobile application, or a laptop acting as a client. These clients send a request such as /api/accounts. The request first reaches the API Gateway. The API Gateway checks the routing information available in the application.yml file. For the /api/accounts path, the routing information points to the ACCOUNTS-SERVICE. The gateway then contacts the Eureka Server to check how many instances of ACCOUNTS-SERVICE are currently running. For example, the Eureka Server may respond that five instances are available. The Eureka Server provides all instance details to the API Gateway. The gateway then uses a round robin strategy to route the incoming request to one of the running instances of the ACCOUNTS-SERVICE. This approach is known as client side load balancing. You will have a Eureka Server, which is a standalone Spring Boot application. All other applications, including the API Gateway and microservices such as Accounts and Cards, register themselves with this server. The startup order is important. First, start the Eureka Server. Next, start the API Gateway. After that, start the individual microservices. You can start multiple instances of a microservice by changing the port number using VM arguments in IntelliJ. This allows you to run any number of instances. Even when multiple instances of a microservice are running, the API Gateway uses a round robin routing strategy to distribute requests among the available instances. Keep learning. This is a very important topic in microservices architecture.