Shulou(Shulou.com)06/01 Report--

This article mainly explains "how to achieve ribbon load balancing". The content of the article is simple and clear, and it is easy to learn and understand. Please follow the editor's ideas to study and learn "how to achieve ribbon load balancing".

Get rid of the dependency of eureke-client.

Rely on ribbon only:

Org.springframework.cloud

Spring-cloud-starter-netflix-ribbon

Configuration file:

Service-sms:

Ribbon:

NFLoadBalancerRuleClassName: com.netflix.loadbalancer.RandomRule

Eureka:

Enable: false

ListOfServers: localhost:8002,localhost:8003

You can configure polling, you can configure random, the above is random, the default is polling.

ZoneAvoidanceRule (Zone tradeoff Strategy): composite judges the performance of the region where the Server is located and the availability of the Server, and polls the selected server.

Other rules:

BestAvailableRule (minimum concurrency strategy): first filter out the service that is in the circuit breaker tripping state due to multiple access failures, and then select a service with the least concurrency. Find the service one by one and ignore it if the circuit breaker is turned on.

RoundRobinRule (polling policy): select a server with a simple poll. Cycle through a server sequentially.

RandomRule (random policy): randomly select a server.

AvailabilityFilteringRule (available filter policy): first filter out the services in the circuit breaker tripping state due to multiple access failures and filter the number of concurrent connections that exceed the valve worth serving, and then install a polling policy for access to the remaining service list.

WeightedResponseTimeRule (response time weighting strategy): the weight of all services is calculated according to the average response time. The faster the response time, the greater the service weight, the higher the probability of being easily selected. At the beginning of startup, if the statistics are not correct, the RoundRobinRule (polling) policy is used. If the statistical information is sufficient, it will automatically switch to WeightedResponseTimeRule. The response time is long, the weight is low and the probability of being selected is low. On the contrary, the same principle. This strategy combines various factors (network, disk, IO, etc.), which directly affect the response time.

RetryRule (retry policy): first obtain the service according to the policy of RoundRobinRule (polling). If the obtained service fails, it will retry at the specified time to obtain the available service. If you fail to get a service multiple times, you will not get the service again. Mainly for a period of time, if the selection of a service is not successful, continue to look for available services until the timeout.

Thank you for your reading. the above is the content of "how to achieve ribbon load balancer". After the study of this article, I believe you have a deeper understanding of how to achieve ribbon load balancer, and the specific usage needs to be verified in practice. Here is, the editor will push for you more related knowledge points of the article, welcome to follow!

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.