一、概述

Zuul的主要功能是路由轉發和過濾器。路由功能是微服務的一部分，比如/client-a/轉發到到a服務，/client-b/轉發到到b服務。zuul預設和Ribbon結合實現了負載均衡的功能。

二、準備

將服務註冊與發現這篇部落格中的Eureka-Client-A工程，複製一份，名字修改為Service-Zuul。

三、工程修改

Gradle依賴修改為

dependencies {
	compile('org.springframework.cloud:spring-cloud-starter-netflix-eureka-client')
	compile('org.springframework.cloud:spring-cloud-starter-zuul:1.4.4.RELEASE')
	compile('org.springframework.boot:spring-boot-starter-web')
	testCompile('org.springframework.boot:spring-boot-starter-test')
}
 

在啟動類上新增@EnableZuulProxy註解，開啟路由功能。

import org.springframework.boot.SpringApplication;
import org.springframework.boot.autoconfigure.SpringBootApplication;
import org.springframework.cloud.netflix.eureka.EnableEurekaClient;
import org.springframework.cloud.netflix.zuul.EnableZuulProxy;

@SpringBootApplication
@EnableEurekaClient
@EnableZuulProxy
public class EurekaZuulApplication
{

	public static void main(String[] args) {
		SpringApplication.run(EurekaZuulApplication.class, args);
	}
}
 

修改application.properties配置檔案，將/client-a/開頭的請求路由到eureka-client-a伺服器

spring.application.name=service-zuul
server.port=10010
eureka.client.serviceUrl.defaultZone=http://localhost:10001/eureka/

zuul.routes.api-a.path: /client-a/**
zuul.routes.api-a.serviceId: eureka-client-a

四、測試

啟動之前的Eureka-Server、Eureka-Client-A和當前的Service-Zuul工程，訪問

五、服務過濾

Zuul不僅有路由的功能，還有服務過濾的功能，做一些攔截驗證。

新建MyFilter類

import com.netflix.zuul.ZuulFilter;
import com.netflix.zuul.context.RequestContext;
import com.netflix.zuul.exception.ZuulException;
import org.slf4j.Logger;
import org.slf4j.LoggerFactory;
import org.springframework.stereotype.Component;

import javax.servlet.http.HttpServletRequest;

/**
 * Created by wzj on 2018/5/24.
 */
@Component
public class MyFilter extends ZuulFilter
{
    private static Logger log = LoggerFactory.getLogger(MyFilter.class);

    /**
     * to classify a filter by type. Standard types in Zuul are "pre" for pre-routing filtering,
     * "route" for routing to an origin, "post" for post-routing filters, "error" for error handling.
     * We also support a "static" type for static responses see  StaticResponseFilter.
     * Any filterType made be created or added and run by calling FilterProcessor.runFilters(type)
     *
     * @return A String representing that type
     */
    @Override
    public String filterType()
    {
        return "pre";
    }

    /**
     * filterOrder() must also be defined for a filter. Filters may have the same  filterOrder if precedence is not
     * important for a filter. filterOrders do not need to be sequential.
     *
     * @return the int order of a filter
     */
    @Override
    public int filterOrder()
    {
        return 0;
    }

    /**
     * a "true" return from this method means that the run() method should be invoked
     *
     * @return true if the run() method should be invoked. false will not invoke the run() method
     */
    @Override
    public boolean shouldFilter()
    {
        return true;
    }

    /**
     * if shouldFilter() is true, this method will be invoked. this method is the core method of a ZuulFilter
     *
     * @return Some arbitrary artifact may be returned. Current implementation ignores it.
     * @throws ZuulException if an error occurs during execution.
     */
    @Override
    public Object run() throws ZuulException
    {
        RequestContext ctx = RequestContext.getCurrentContext();
        HttpServletRequest request = ctx.getRequest();
        log.info(String.format("%s >>> %s", request.getMethod(), request.getRequestURL().toString()));
        Object accessToken = request.getParameter("token");
        if (accessToken == null)
        {
            log.warn("token is empty");
            ctx.setSendZuulResponse(false);
            ctx.setResponseStatusCode(401);
            try
            {
                ctx.getResponse().getWriter().write("token is empty");
            }
            catch (Exception e)
            {
            }

            return null;
        }
        log.info("ok");
        return null;
    }
}

filterType：返回一個字串代表過濾器的型別，在zuul中定義了四種不同生命週期的過濾器型別，具體如下： 

• pre：路由之前
• routing：路由之時
• post： 路由之後
• error：傳送錯誤呼叫
• filterOrder：過濾的順序
• shouldFilter：這裡可以寫邏輯判斷，是否要過濾，本文true,永遠過濾。
• run：過濾器的具體邏輯。可用很複雜，包括查sql，nosql去判斷該請求到底有沒有許可權訪問。