为了方便查看具体执行了哪个服务提供者,我们再Controller控制器的方法里搞个打印语句;
相关代码如下
相关pom
<properties> <java.version>1.8</java.version> </properties> <dependencies> <dependency> <groupId>com.javaxl</groupId> <artifactId>microservice-common</artifactId> </dependency> <dependency> <groupId>org.springframework.boot</groupId> <artifactId>spring-boot-starter-web</artifactId> </dependency> <dependency> <groupId>org.springframework.boot</groupId> <artifactId>spring-boot-starter-test</artifactId> <scope>test</scope> </dependency> <dependency> <groupId>org.springframework.boot</groupId> <artifactId>spring-boot-starter-data-jpa</artifactId> </dependency> <dependency> <groupId>mysql</groupId> <artifactId>mysql-connector-java</artifactId> </dependency> <dependency> <groupId>org.springframework.boot</groupId> <artifactId>spring-boot-starter-tomcat</artifactId> </dependency> <dependency> <groupId>com.alibaba</groupId> <artifactId>druid-spring-boot-starter</artifactId> </dependency> <!-- 修改后立即生效,热部署 --> <dependency> <groupId>org.springframework</groupId> <artifactId>springloaded</artifactId> </dependency> <dependency> <groupId>org.springframework.boot</groupId> <artifactId>spring-boot-devtools</artifactId> </dependency> <dependency> <groupId>com.javaxl</groupId> <artifactId>microservice-common</artifactId> <version>1.0-SNAPSHOT</version> <scope>compile</scope> </dependency> <!--添加注册中心Eureka相关配置--> <dependency> <groupId>org.springframework.cloud</groupId> <artifactId>spring-cloud-starter-eureka</artifactId> </dependency> <dependency> <groupId>org.springframework.cloud</groupId> <artifactId>spring-cloud-starter-config</artifactId> </dependency> <!-- actuator监控引入 --> <dependency> <groupId>org.springframework.boot</groupId> <artifactId>spring-boot-starter-actuator</artifactId> </dependency> </dependencies>
Yml文件
--- server: port: 1001 context-path: / spring: datasource: type: com.alibaba.druid.pool.DruidDataSource driver-class-name: com.mysql.jdbc.Driver url: jdbc:mysql://localhost:3306/mybatis_ssm?useUnicode=true&characterEncoding=utf8 username: mybatis_ssm password: xiaoli jpa: hibernate: ddl-auto: update show-sql: true application: name: microservice-student profiles: provider-1001 eureka: instance: hostname: localhost appname: microservice-student instance-id: microservice-student:1001 prefer-ip-address: true client: service-url: defaultZone: http://eureka2001.javaxl.com:2001/eureka/,http://eureka2002.javaxl.com:2002/eureka/,http://eureka2003.javaxl.com:2003/eureka/ info: groupId: com.javaxl.testSpringcloud artifactId: microservice-student-provider-1001 version: 1.0-SNAPSHOT userName: http://47.100.191.44 phone: 123456 --- server: port: 1002 context-path: / spring: datasource: type: com.alibaba.druid.pool.DruidDataSource driver-class-name: com.mysql.jdbc.Driver url: jdbc:mysql://localhost:3306/mybatis_ssm?useUnicode=true&characterEncoding=utf8 username: mybatis_ssm password: xiaoli jpa: hibernate: ddl-auto: update show-sql: true application: name: microservice-student profiles: provider-1002 eureka: instance: hostname: localhost appname: microservice-student instance-id: microservice-student:1002 prefer-ip-address: true client: service-url: defaultZone: http://eureka2001.javaxl.com:2001/eureka/,http://eureka2002.javaxl.com:2002/eureka/,http://eureka2003.javaxl.com:2003/eureka/ info: groupId: com.javaxl.testSpringcloud artifactId: microservice-student-provider-1002 version: 1.0-SNAPSHOT userName: http://47.100.191.44 phone: 123456 --- server: port: 1003 context-path: / spring: datasource: type: com.alibaba.druid.pool.DruidDataSource driver-class-name: com.mysql.jdbc.Driver url: jdbc:mysql://localhost:3306/mybatis_ssm?useUnicode=true&characterEncoding=utf8 username: mybatis_ssm password: xiaoli jpa: hibernate: ddl-auto: update show-sql: true application: name: microservice-student profiles: provider-1003 eureka: instance: hostname: localhost appname: microservice-student instance-id: microservice-student:1003 prefer-ip-address: true client: service-url: defaultZone: http://eureka2001.javaxl.com:2001/eureka/,http://eureka2002.javaxl.com:2002/eureka/,http://eureka2003.javaxl.com:2003/eureka/ info: groupId: com.javaxl.testSpringcloud artifactId: microservice-student-provider-1003 version: 1.0-SNAPSHOT userName: http://47.100.191.44 phone: 123456
启动类
package com.javaxl.microservicestudentprovider; import org.springframework.boot.SpringApplication; import org.springframework.boot.autoconfigure.SpringBootApplication; import org.springframework.boot.autoconfigure.domain.EntityScan; import org.springframework.cloud.netflix.eureka.EnableEurekaClient; @EntityScan("com.javaxl.*.*") @EnableEurekaClient @SpringBootApplication public class MicroserviceStudentProviderApplication { public static void main(String[] args) { SpringApplication.run(MicroserviceStudentProviderApplication.class, args); } }
StudentProviderController.java
@Value("${server.port}") private String port; @RequestMapping("/ribbon") public String ribbon(){ return "工号【"+port+"】正在为您服务"; }
StudentConsumerController.java
@RequestMapping("/ribbon") public String ribbon(){ return restTemplate.getForObject(SERVER_IP_PORT + "/student/ribbon", String.class); }
先测试服务提供者:
http://localhost:1001/student/list
http://localhost:1002/student/list
http://localhost:1003/student/list
看看是否有结果;
再测试下 eureka:
http://eureka2001.javaxl.com:2001/
http://eureka2002.javaxl.com:2002/
http://eureka2003.javaxl.com:2003/
有这种的话,就说明没问题;
然后再启动服务消费者:
http://localhost/student/list 多刷新几次 看控制台,我们看到 有默认的轮询策略,访问对应的服务提供者;
但是这种默认的轮询策略肯定是不能满足实际需求的,比如有3个服务提供者,突然挂了一个,这样的话,默认轮询 ,总有1/3的概率访问失败; 所以我们看下ribbon默认给我们提供的策略有哪些;
策略名 | 策略声明 | 策略描述 | 实现说明 |
BestAvailableRule | public class BestAvailableRule extends ClientConfigEnabledRoundRobinRule | 选择一个最小的并发请求的server | 逐个考察Server,如果Server被tripped了,则忽略,在选择其中ActiveRequestsCount最小的server |
AvailabilityFilteringRule | public class AvailabilityFilteringRule extends PredicateBasedRule | 过滤掉那些因为一直连接失败的被标记为circuit tripped的后端server,并过滤掉那些高并发的的后端server(active connections 超过配置的阈值) | 使用一个AvailabilityPredicate来包含过滤server的逻辑,其实就就是检查status里记录的各个server的运行状态 |
WeightedResponseTimeRule | public class WeightedResponseTimeRule extends RoundRobinRule | 根据响应时间分配一个weight,响应时间越长,weight越小,被选中的可能性越低。 | 一个后台线程定期的从status里面读取评价响应时间,为每个server计算一个weight。Weight的计算也比较简单responsetime 减去每个server自己平均的responsetime是server的权重。当刚开始运行,没有形成status时,使用roubine策略选择server。 |
RetryRule | public class RetryRule extends AbstractLoadBalancerRule | 对选定的负载均衡策略机上重试机制。 | 在一个配置时间段内当选择server不成功,则一直尝试使用subRule的方式选择一个可用的server |
RoundRobinRule | public class RoundRobinRule extends AbstractLoadBalancerRule | roundRobin方式轮询选择server | 轮询index,选择index对应位置的server |
RandomRule | public class RandomRule extends AbstractLoadBalancerRule | 随机选择一个server | 在index上随机,选择index对应位置的server |
ZoneAvoidanceRule | public class ZoneAvoidanceRule extends PredicateBasedRule | 复合判断server所在区域的性能和server的可用性选择server | 使用ZoneAvoidancePredicate和AvailabilityPredicate来判断是否选择某个server,前一个判断判定一个zone的运行性能是否可用,剔除不可用的zone(的所有server),AvailabilityPredicate用于过滤掉连接数过多的Server。 |
默认7个策略,根据具体产品需求,我们选用;
代码中如何假如呢;
服务消费端 SpringCloudConfig配置类
指定IRule实现;
这里我们演示用 RetryRule,大伙可以自行测试;
package com.javaxl.microservicestudentconsumer80.config; import com.netflix.loadbalancer.IRule; import com.netflix.loadbalancer.RetryRule; import org.springframework.cloud.client.loadbalancer.LoadBalanced; import org.springframework.context.annotation.Bean; import org.springframework.context.annotation.Configuration; import org.springframework.web.client.RestTemplate; @Configuration public class SpringCloudConfig { @LoadBalanced // 引入ribbon负载均衡 @Bean public RestTemplate getRestTemplate() { return new RestTemplate(); } /** * 自定义轮询算法 * @return */ @Bean public IRule myRule(){ return new RetryRule(); } }
用法很简单;
备案号:湘ICP备19000029号
Copyright © 2018-2019 javaxl晓码阁 版权所有