Feign之源码剖析

青旅半醒 2023-06-28 04:53 18阅读 0赞

附:SpringCloud之系列汇总跳转地址

什么是Feign

Feign是由Retrofit,JAXRS-2.0和WebSocket启发的一个java到http客户端绑定。 Feign的主要目标是将Java Http Clients变得简单。

写一个Feign

简单的实现一个Feign客户端,首先通过@FeignClient,客户端,其中value为调用其他服务的名称,FeignConfig.class为FeignClient的配置文件,代码如下:

  1. @FeignClient(value = "service-hi",configuration = FeignConfig.class)
  2. public interface SchedualServiceHi {
  3. @GetMapping(value = "/hi")
  4. String sayHiFromClientOne(@RequestParam(value = "name") String name);
  5. }

其配置文件如下:

  1. @Configuration
  2. public class FeignConfig {
  3. @Bean
  4. public Retryer feignRetryer() {
  5. return new Retryer.Default(100, SECONDS.toMillis(1), 5);
  6. }
  7. }

查看FeignClient的源码,其代码如下:

  1. @Target(ElementType.TYPE)
  2. @Retention(RetentionPolicy.RUNTIME)
  3. @Documented
  4. public @interface FeignClient {
  5. @AliasFor("name")
  6. String value() default "";
  7. @AliasFor("value")
  8. String name() default "";
  9. @AliasFor("value")
  10. String name() default "";
  11. String url() default "";
  12. boolean decode404() default false;
  13. Class<?>[] configuration() default {};
  14. Class<?> fallback() default void.class;
  15. Class<?> fallbackFactory() default void.class;
  16. }
  17. String path() default "";
  18. boolean primary() default true;

feign 用于声明具有该接口的REST客户端的接口的注释应该是创建(例如用于自动连接到另一个组件。 如果功能区可用,那将是 用于负载平衡后端请求,并且可以配置负载平衡器 使用与伪装客户端相同名称(即值)@RibbonClient 。

其中value()和name()一样,是被调用的 service的名称。 url(),直接填写硬编码的url,decode404()即404是否被解码,还是抛异常;configuration(),标明FeignClient的配置类,默认的配置类为FeignClientsConfiguration类,可以覆盖Decoder、Encoder和Contract等信息,进行自定义配置。fallback(),填写熔断器的信息类。

FeignClient的配置

默认的配置类为FeignClientsConfiguration,这个类在spring-cloud-netflix-core的jar包下,打开这个类,可以发现它是一个配置类,注入了很多的相关配置的bean,包括feignRetryer、FeignLoggerFactory、FormattingConversionService等,其中还包括了Decoder、Encoder、Contract,如果这三个bean在没有注入的情况下,会自动注入默认的配置。

  • Decoder feignDecoder: ResponseEntityDecoder(这是对SpringDecoder的封装)
  • Encoder feignEncoder: SpringEncoder
  • Logger feignLogger: Slf4jLogger
  • Contract feignContract: SpringMvcContract
  • Feign.Builder feignBuilder: HystrixFeign.Builder

代码如下:

  1. @Configuration
  2. public class FeignClientsConfiguration {
  3. ...//省略代码
  4. @Bean
  5. @ConditionalOnMissingBean
  6. public Decoder feignDecoder() {
  7. return new ResponseEntityDecoder(new SpringDecoder(this.messageConverters));
  8. }
  9. @Bean
  10. @ConditionalOnMissingBean
  11. public Encoder feignEncoder() {
  12. return new SpringEncoder(this.messageConverters);
  13. }
  14. @Bean
  15. @ConditionalOnMissingBean
  16. public Contract feignContract(ConversionService feignConversionService) {
  17. return new SpringMvcContract(this.parameterProcessors, feignConversionService);
  18. }
  19. ...//省略代码
  20. }

重写配置:

你可以重写FeignClientsConfiguration中的bean,从而达到自定义配置的目的,比如FeignClientsConfiguration的默认重试次数为Retryer.NEVER_RETRY,即不重试,那么希望做到重写,代码如下:

  1. @Configuration
  2. public class FeignConfig {
  3. @Bean
  4. public Retryer feignRetryer() {
  5. return new Retryer.Default(100, SECONDS.toMillis(1), 5);
  6. }
  7. }

在上述代码更改了该FeignClient的重试次数,重试间隔为100ms,最大重试时间为1s,重试次数为5次。

Feign的工作原理

feign是一个伪客户端,即它不做任何的请求处理。Feign通过处理注解生成request,从而实现简化HTTP API开发的目的,即开发人员可以使用注解的方式定制request api模板,在发送http request请求之前,feign通过处理注解的方式替换掉request模板中的参数,这种实现方式显得更为直接、可理解。

通过包扫描注入FeignClient的bean,该源码在FeignClientsRegistrar类: 首先在启动配置上检查是否有@EnableFeignClients注解,如果有该注解,则开启包扫描,扫描被@FeignClient注解接口。代码如下:

  1. private void registerDefaultConfiguration(AnnotationMetadata metadata,
  2. BeanDefinitionRegistry registry) {
  3. Map<String, Object> defaultAttrs = metadata
  4. .getAnnotationAttributes(EnableFeignClients.class.getName(), true);
  5. if (defaultAttrs != null && defaultAttrs.containsKey("defaultConfiguration")) {
  6. String name;
  7. if (metadata.hasEnclosingClass()) {
  8. name = "default." + metadata.getEnclosingClassName();
  9. }
  10. else {
  11. name = "default." + metadata.getClassName();
  12. }
  13. registerClientConfiguration(registry, name,
  14. defaultAttrs.get("defaultConfiguration"));
  15. }
  16. }

扫描到FeignClient后,将信息取出,以bean的形式注入到ioc容器中,源码如下:

  1. public void registerFeignClients(AnnotationMetadata metadata,
  2. BeanDefinitionRegistry registry) {
  3. ClassPathScanningCandidateComponentProvider scanner = getScanner();
  4. scanner.setResourceLoader(this.resourceLoader);
  5. Set<String> basePackages;
  6. Map<String, Object> attrs = metadata
  7. .getAnnotationAttributes(EnableFeignClients.class.getName());
  8. AnnotationTypeFilter annotationTypeFilter = new AnnotationTypeFilter(
  9. FeignClient.class);
  10. final Class<?>[] clients = attrs == null ? null
  11. : (Class<?>[]) attrs.get("clients");
  12. if (clients == null || clients.length == 0) {
  13. scanner.addIncludeFilter(annotationTypeFilter);
  14. basePackages = getBasePackages(metadata);
  15. }
  16. else {
  17. final Set<String> clientClasses = new HashSet<>();
  18. basePackages = new HashSet<>();
  19. for (Class<?> clazz : clients) {
  20. basePackages.add(ClassUtils.getPackageName(clazz));
  21. clientClasses.add(clazz.getCanonicalName());
  22. }
  23. AbstractClassTestingTypeFilter filter = new AbstractClassTestingTypeFilter() {
  24. @Override
  25. protected boolean match(ClassMetadata metadata) {
  26. String cleaned = metadata.getClassName().replaceAll("\\$", ".");
  27. return clientClasses.contains(cleaned);
  28. }
  29. };
  30. scanner.addIncludeFilter(
  31. new AllTypeFilter(Arrays.asList(filter, annotationTypeFilter)));
  32. }
  33. for (String basePackage : basePackages) {
  34. Set<BeanDefinition> candidateComponents = scanner
  35. .findCandidateComponents(basePackage);
  36. for (BeanDefinition candidateComponent : candidateComponents) {
  37. if (candidateComponent instanceof AnnotatedBeanDefinition) {
  38. // verify annotated class is an interface
  39. AnnotatedBeanDefinition beanDefinition = (AnnotatedBeanDefinition) candidateComponent;
  40. AnnotationMetadata annotationMetadata = beanDefinition.getMetadata();
  41. Assert.isTrue(annotationMetadata.isInterface(),
  42. "@FeignClient can only be specified on an interface");
  43. Map<String, Object> attributes = annotationMetadata
  44. .getAnnotationAttributes(
  45. FeignClient.class.getCanonicalName());
  46. String name = getClientName(attributes);
  47. registerClientConfiguration(registry, name,
  48. attributes.get("configuration"));
  49. registerFeignClient(registry, annotationMetadata, attributes);
  50. }
  51. }
  52. }
  53. }
  54. private void registerFeignClient(BeanDefinitionRegistry registry,
  55. AnnotationMetadata annotationMetadata, Map<String, Object> attributes) {
  56. String className = annotationMetadata.getClassName();
  57. BeanDefinitionBuilder definition = BeanDefinitionBuilder
  58. .genericBeanDefinition(FeignClientFactoryBean.class);
  59. validate(attributes);
  60. definition.addPropertyValue("url", getUrl(attributes));
  61. definition.addPropertyValue("path", getPath(attributes));
  62. String name = getName(attributes);
  63. definition.addPropertyValue("name", name);
  64. definition.addPropertyValue("type", className);
  65. definition.addPropertyValue("decode404", attributes.get("decode404"));
  66. definition.addPropertyValue("fallback", attributes.get("fallback"));
  67. definition.addPropertyValue("fallbackFactory", attributes.get("fallbackFactory"));
  68. definition.setAutowireMode(AbstractBeanDefinition.AUTOWIRE_BY_TYPE);
  69. String alias = name + "FeignClient";
  70. AbstractBeanDefinition beanDefinition = definition.getBeanDefinition();
  71. boolean primary = (Boolean)attributes.get("primary"); // has a default, won't be null
  72. beanDefinition.setPrimary(primary);
  73. String qualifier = getQualifier(attributes);
  74. if (StringUtils.hasText(qualifier)) {
  75. alias = qualifier;
  76. }
  77. BeanDefinitionHolder holder = new BeanDefinitionHolder(beanDefinition, className,
  78. new String[] { alias });
  79. BeanDefinitionReaderUtils.registerBeanDefinition(holder, registry);
  80. }

注入bean之后,通过jdk的代理,当请求Feign Client的方法时会被拦截,代码在ReflectiveFeign类,代码如下:

  1. public <T> T newInstance(Target<T> target) {
  2. Map<String, MethodHandler> nameToHandler = targetToHandlersByName.apply(target);
  3. Map<Method, MethodHandler> methodToHandler = new LinkedHashMap<Method, MethodHandler>();
  4. List<DefaultMethodHandler> defaultMethodHandlers = new LinkedList<DefaultMethodHandler>();
  5. for (Method method : target.type().getMethods()) {
  6. if (method.getDeclaringClass() == Object.class) {
  7. continue;
  8. } else if(Util.isDefault(method)) {
  9. DefaultMethodHandler handler = new DefaultMethodHandler(method);
  10. defaultMethodHandlers.add(handler);
  11. methodToHandler.put(method, handler);
  12. } else {
  13. methodToHandler.put(method, nameToHandler.get(Feign.configKey(target.type(), method)));
  14. }
  15. }
  16. InvocationHandler handler = factory.create(target, methodToHandler);
  17. T proxy = (T) Proxy.newProxyInstance(target.type().getClassLoader(), new Class<?>[]{target.type()}, handler);
  18. for(DefaultMethodHandler defaultMethodHandler : defaultMethodHandlers) {
  19. defaultMethodHandler.bindTo(proxy);
  20. }
  21. return proxy;
  22. }

在SynchronousMethodHandler类进行拦截处理,当被拦截会根据参数生成RequestTemplate对象,该对象就是http请求的模板,代码如下:

  1. @Override
  2. public Object invoke(Object[] argv) throws Throwable {
  3. RequestTemplate template = buildTemplateFromArgs.create(argv);
  4. Retryer retryer = this.retryer.clone();
  5. while (true) {
  6. try {
  7. return executeAndDecode(template);
  8. } catch (RetryableException e) {
  9. retryer.continueOrPropagate(e);
  10. if (logLevel != Logger.Level.NONE) {
  11. logger.logRetry(metadata.configKey(), logLevel);
  12. }
  13. continue;
  14. }
  15. }
  16. }

其中有个executeAndDecode()方法,该方法是通RequestTemplate生成Request请求对象,然后根据用client获取response。

  1. Object executeAndDecode(RequestTemplate template) throws Throwable {
  2. Request request = targetRequest(template);
  3. ...//省略代码
  4. response = client.execute(request, options);
  5. ...//省略代码
  6. }

Client组件

其中Client组件是一个非常重要的组件,Feign最终发送request请求以及接收response响应,都是由Client组件完成的,其中Client的实现类,只要有Client.Default,该类由HttpURLConnnection实现网络请求,另外还支持HttpClient、Okhttp.

首先来看以下在FeignRibbonClient的自动配置类,FeignRibbonClientAutoConfiguration ,主要在工程启动的时候注入一些bean,其代码如下:

  1. @ConditionalOnClass({ ILoadBalancer.class, Feign.class })
  2. @Configuration
  3. @AutoConfigureBefore(FeignAutoConfiguration.class)
  4. public class FeignRibbonClientAutoConfiguration {
  5. @Bean
  6. @ConditionalOnMissingBean
  7. public Client feignClient(CachingSpringLoadBalancerFactory cachingFactory,
  8. SpringClientFactory clientFactory) {
  9. return new LoadBalancerFeignClient(new Client.Default(null, null),
  10. cachingFactory, clientFactory);
  11. }
  12. }

在缺失配置feignClient的情况下,会自动注入new Client.Default(),跟踪Client.Default()源码,它使用的网络请求框架为HttpURLConnection,代码如下:

  1. @Override
  2. public Response execute(Request request, Options options) throws IOException {
  3. HttpURLConnection connection = convertAndSend(request, options);
  4. return convertResponse(connection).toBuilder().request(request).build();
  5. }

怎么在feign中使用HttpClient,查看FeignRibbonClientAutoConfiguration的源码

  1. @ConditionalOnClass({ ILoadBalancer.class, Feign.class })
  2. @Configuration
  3. @AutoConfigureBefore(FeignAutoConfiguration.class)
  4. public class FeignRibbonClientAutoConfiguration {
  5. ...//省略代码
  6. @Configuration
  7. @ConditionalOnClass(ApacheHttpClient.class)
  8. @ConditionalOnProperty(value = "feign.httpclient.enabled", matchIfMissing = true)
  9. protected static class HttpClientFeignLoadBalancedConfiguration {
  10. @Autowired(required = false)
  11. private HttpClient httpClient;
  12. @Bean
  13. @ConditionalOnMissingBean(Client.class)
  14. public Client feignClient(CachingSpringLoadBalancerFactory cachingFactory,
  15. SpringClientFactory clientFactory) {
  16. ApacheHttpClient delegate;
  17. if (this.httpClient != null) {
  18. delegate = new ApacheHttpClient(this.httpClient);
  19. }
  20. else {
  21. delegate = new ApacheHttpClient();
  22. }
  23. return new LoadBalancerFeignClient(delegate, cachingFactory, clientFactory);
  24. }
  25. }
  26. ...//省略代码
  27. }

从代码@ConditionalOnClass(ApacheHttpClient.class)注解可知道,只需要在pom文件加上HttpClient的classpath就行了,另外需要在配置文件上加上feign.httpclient.enabled为true,从 @ConditionalOnProperty注解可知,这个可以不写,在默认的情况下就为true.

在pom文件加上:

  1. <dependency>
  2. <groupId>com.netflix.feign</groupId>
  3. <artifactId>feign-httpclient</artifactId>
  4. <version>RELEASE</version>
  5. </dependency>

同理,如果想要feign使用Okhttp,则只需要在pom文件上加上feign-okhttp的依赖:

  1. <dependency>
  2. <groupId>com.netflix.feign</groupId>
  3. <artifactId>feign-okhttp</artifactId>
  4. <version>RELEASE</version>
  5. </dependency>

feign的负载均衡是怎么样实现的呢?

通过上述的FeignRibbonClientAutoConfiguration类配置Client的类型(httpurlconnection,okhttp和httpclient)时候,可知最终向容器注入的是LoadBalancerFeignClient,即负载均衡客户端。现在来看下LoadBalancerFeignClient的代码:

  1. @Override
  2. public Response execute(Request request, Request.Options options) throws IOException {
  3. try {
  4. URI asUri = URI.create(request.url());
  5. String clientName = asUri.getHost();
  6. URI uriWithoutHost = cleanUrl(request.url(), clientName);
  7. FeignLoadBalancer.RibbonRequest ribbonRequest = new FeignLoadBalancer.RibbonRequest(
  8. this.delegate, request, uriWithoutHost);
  9. IClientConfig requestConfig = getClientConfig(options, clientName);
  10. return lbClient(clientName).executeWithLoadBalancer(ribbonRequest,
  11. requestConfig).toResponse();
  12. }
  13. catch (ClientException e) {
  14. IOException io = findIOException(e);
  15. if (io != null) {
  16. throw io;
  17. }
  18. throw new RuntimeException(e);
  19. }
  20. }

其中有个executeWithLoadBalancer()方法,即通过负载均衡的方式请求。

  1. public T executeWithLoadBalancer(final S request, final IClientConfig requestConfig) throws ClientException {
  2. RequestSpecificRetryHandler handler = getRequestSpecificRetryHandler(request, requestConfig);
  3. LoadBalancerCommand<T> command = LoadBalancerCommand.<T>builder()
  4. .withLoadBalancerContext(this)
  5. .withRetryHandler(handler)
  6. .withLoadBalancerURI(request.getUri())
  7. .build();
  8. try {
  9. return command.submit(
  10. new ServerOperation<T>() {
  11. @Override
  12. public Observable<T> call(Server server) {
  13. URI finalUri = reconstructURIWithServer(server, request.getUri());
  14. S requestForServer = (S) request.replaceUri(finalUri);
  15. try {
  16. return Observable.just(AbstractLoadBalancerAwareClient.this.execute(requestForServer, requestConfig));
  17. }
  18. catch (Exception e) {
  19. return Observable.error(e);
  20. }
  21. }
  22. })
  23. .toBlocking()
  24. .single();
  25. } catch (Exception e) {
  26. Throwable t = e.getCause();
  27. if (t instanceof ClientException) {
  28. throw (ClientException) t;
  29. } else {
  30. throw new ClientException(e);
  31. }
  32. }
  33. }

其中服务在submit()方法上,点击submit进入具体的方法,这个方法是LoadBalancerCommand的方法:

  1. Observable<T> o =
  2. (server == null ? selectServer() : Observable.just(server))
  3. .concatMap(new Func1<Server, Observable<T>>() {
  4. @Override
  5. // Called for each server being selected
  6. public Observable<T> call(Server server) {
  7. context.setServer(server);
  8. }}

上述代码中有个selectServe(),该方法是选择服务的进行负载均衡的方法,代码如下:

  1. private Observable<Server> selectServer() {
  2. return Observable.create(new OnSubscribe<Server>() {
  3. @Override
  4. public void call(Subscriber<? super Server> next) {
  5. try {
  6. Server server = loadBalancerContext.getServerFromLoadBalancer(loadBalancerURI, loadBalancerKey);
  7. next.onNext(server);
  8. next.onCompleted();
  9. } catch (Exception e) {
  10. next.onError(e);
  11. }
  12. }
  13. });
  14. }

最终负载均衡交给loadBalancerContext来处理,即之前讲述的Ribbon,在这里不再重复。

总结

总的来说,Feign的源码实现的过程如下:

  • 首先通过@EnableFeignClients注解开启FeignClient
  • 根据Feign的规则实现接口,并加@FeignClient注解
  • 程序启动后,会进行包扫描,扫描所有的@FeignClient的注解的类,并将这些信息注入到ioc容器中
  • 当接口的方法被调用,通过jdk的代理,来生成具体的RequestTemplate
  • RequestTemplate再生成Request
  • Request交给Client去处理,其中Client可以是HttpUrlConnection、HttpClient,也可以是Okhttp
  • 最后Client被封装到LoadBalanceClient类,这个类结合Ribbon做到了负载均衡

附:SpringCloud之系列汇总跳转地址

发表评论

表情:
评论列表 (有 0 条评论,18人围观)

还没有评论,来说两句吧...

相关阅读

    相关 Redis剖析RDB

    我们小学三年级的时候就知道,redis是一个纯内存存储的中间件,那它宕机会怎么样?数据会丢失吗?答案是可以不丢。 事实上redis为了保证宕机时数据不丢失,提供了两种数据持久化