Public dependence in engineering pom
<properties>
<project.build.sourceEncoding>UTF-8</project.build.sourceEncoding>
<project.reporting.outputEncoding>UTF-8</project.reporting.outputEncoding>
<java.version>1.8</java.version>
<spring-cloud.version>Finchley.RELEASE</spring-cloud.version>
</properties>
<dependencyManagement>
<dependencies>
<dependency>
<groupId>org.springframework.cloud</groupId>
<artifactId>spring-cloud-dependencies</artifactId>
<version>${spring-cloud.version}</version>
<type>pom</type>
<scope>import</scope>
</dependency>
</dependencies>
</dependencyManagement>
1. Eureka Server Project
Start four instances and configure two zones, namely zone1 and zone2. Each zone requires two eureka server instances. The two zones are configured on the same region, namely region-east.
1.1. Ereka-server project pom file:
<!--Plus the public dependence on the header of the article-->
<dependencies> <dependency> <groupId>org.springframework.cloud</groupId> <artifactId>spring-cloud-starter-netflix-eureka-server</artifactId> </dependency> </dependencies> <build> <plugins> <plugin> <groupId>org.springframework.boot</groupId> <artifactId>spring-boot-maven-plugin</artifactId> </plugin> </plugins> </build>
1.2. Ereka-server Project Startup Class
import org.springframework.boot.SpringApplication; import org.springframework.boot.autoconfigure.SpringBootApplication; import org.springframework.cloud.netflix.eureka.server.EnableEurekaServer; @SpringBootApplication @EnableEurekaServer public class EurekaServerApplication { public static void main(String[] args) { SpringApplication.run(EurekaServerApplication.class, args); } }
1.3, eureka-server project configuration file, path: eureka-server src main resources 5 files: application-zone 1a.yml, application-zone 1b.yml, application-zone 2a.yml, application-zone 2b.yml, application.yml
application-zone1a.yml:
server: port: 8761 spring: application: name: eureka-server eureka: instance: hostname: localhost preferIpAddress: true metadataMap.zone: zone1 client: register-with-eureka: true fetch-registry: true region: region-east service-url: zone1: http://localhost:8761/eureka/,http://localhost:8762/eureka/ zone2: http://localhost:8763/eureka/,http://localhost:8764/eureka/ availability-zones: region-east: zone1,zone2 server: waitTimeInMsWhenSyncEmpty: 0 enableSelfPreservation: false
application-zone1b.yml
server: port: 8762 spring: application: name: eureka-server eureka: instance: hostname: localhost preferIpAddress: true metadataMap.zone: zone1 client: register-with-eureka: true fetch-registry: true region: region-east service-url: zone1: http://localhost:8761/eureka/,http://localhost:8762/eureka/ zone2: http://localhost:8763/eureka/,http://localhost:8764/eureka/ availability-zones: region-east: zone1,zone2 server: waitTimeInMsWhenSyncEmpty: 0 enableSelfPreservation: false
application-zone2a.yml
server: port: 8763 spring: application: name: eureka-server eureka: instance: hostname: localhost preferIpAddress: true metadataMap.zone: zone2 client: register-with-eureka: true fetch-registry: true region: region-east service-url: zone1: http://localhost:8761/eureka/,http://localhost:8762/eureka/ zone2: http://localhost:8763/eureka/,http://localhost:8764/eureka/ availability-zones: region-east: zone1,zone2 server: waitTimeInMsWhenSyncEmpty: 0 enableSelfPreservation: false
application-zone2b.yml
server: port: 8764 spring: application: name: eureka-server eureka: instance: hostname: localhost preferIpAddress: true metadataMap.zone: zone2 client: register-with-eureka: true fetch-registry: true region: region-east service-url: zone1: http://localhost:8761/eureka/,http://localhost:8762/eureka/ zone2: http://localhost:8763/eureka/,http://localhost:8764/eureka/ availability-zones: region-east: zone1,zone2 server: waitTimeInMsWhenSyncEmpty: 0 enableSelfPreservation: false
application.yml
eureka: server: use-read-only-response-cache: false response-cache-auto-expiration-in-seconds: 10 management: endpoints: web: exposure: include: '*'
As can be seen from the four configuration files above, we set up the zone of each instance through eureka.instance.metadataMap.zone, and then use these four configurations to start four eureka server instances:
//Start command
mvn spring-boot:run -Dspring.profiles.active=zone1a mvn spring-boot:run -Dspring.profiles.active=zone1b mvn spring-boot:run -Dspring.profiles.active=zone2a mvn spring-boot:run -Dspring.profiles.active=zone2b
2. Eureka Client Project
Two Eureka clents are configured here, belonging to zone1 and zone2, respectively.
2.1. Ereka-client project pom file
<!--Plus article header public configuration-->
<dependencies> <dependency> <groupId>org.springframework.cloud</groupId> <artifactId>spring-cloud-starter-netflix-eureka-client</artifactId> </dependency> </dependencies> <build> <plugins> <plugin> <groupId>org.springframework.boot</groupId> <artifactId>spring-boot-maven-plugin</artifactId> </plugin> </plugins> </build>
2.1. Ereka-client Project Startup Class
import org.springframework.boot.SpringApplication; import org.springframework.boot.autoconfigure.SpringBootApplication; import org.springframework.cloud.client.discovery.EnableDiscoveryClient; @SpringBootApplication @EnableDiscoveryClient public class EurekaClientApplication { public static void main(String[] args) { SpringApplication.run(EurekaClientApplication.class, args); } }
2.2, eureka-client project configuration file, path: eureka-client src main resources three files: application.yml, application-zone 1.yml, application-zone 2.yml
application.yml:
#All endpoints are exposed here for later verification.
management:
endpoints:
web:
exposure:
include: '*'
application-zone1.yml:
server: port: 8081 spring: application: name: client eureka: instance: metadataMap.zone: zone1 client: register-with-eureka: true fetch-registry: true region: region-east service-url: zone1: http://localhost:8761/eureka/,http://localhost:8762/eureka/ zone2: http://localhost:8763/eureka/,http://localhost:8764/eureka/ availability-zones: region-east: zone1,zone2
application-zone2.yml:
server: port: 8082 spring: application: name: client eureka: instance: metadataMap.zone: zone2 client: register-with-eureka: true fetch-registry: true region: region-east service-url: zone1: http://localhost:8761/eureka/,http://localhost:8762/eureka/ zone2: http://localhost:8763/eureka/,http://localhost:8764/eureka/ availability-zones: region-east: zone1,zone2
2.3. Start the eureka client, execute the command, and start two instances:
mvn spring-boot:run -Dspring.profiles.active=zone1 mvn spring-boot:run -Dspring.profiles.active=zone2
3. Zuul Gateway Project
A new zuul Gateway project is created here to demonstrate Zone Affinity features in the zone attribute of metadataMap.
3.1. zuul gateway project, pom file:
<!--Plus the public dependence on the header of the article-->
<dependencies> <dependency> <groupId>org.springframework.cloud</groupId> <artifactId>spring-cloud-starter-netflix-zuul</artifactId> </dependency> <dependency> <groupId>org.springframework.cloud</groupId> <artifactId>spring-cloud-starter-netflix-eureka-client</artifactId> </dependency> </dependencies> <build> <plugins> <plugin> <groupId>org.springframework.boot</groupId> <artifactId>spring-boot-maven-plugin</artifactId> </plugin> </plugins> </build>
3.2. zuul gateway project startup class:
import org.springframework.boot.SpringApplication; import org.springframework.boot.autoconfigure.SpringBootApplication; import org.springframework.cloud.client.discovery.EnableDiscoveryClient; import org.springframework.cloud.netflix.zuul.EnableZuulProxy; @SpringBootApplication @EnableDiscoveryClient @EnableZuulProxy public class ZuulGatewayApplication { public static void main(String[] args) { SpringApplication.run(ZuulGatewayApplication.class, args); } }
3.3, zuul gateway project configuration file, path: zuul-gateway src main resources a total of three files: application.yml, application-zone 1.yml, application-zone 2.yml
application.yml:
spring: application: name: zuul-gateway management: endpoints: web: exposure: include: '*'
application-zone1.yml:
server: port: 10001 eureka: instance: metadataMap.zone: zone1 client: register-with-eureka: true fetch-registry: true region: region-east service-url: zone1: http://localhost:8761/eureka/,http://localhost:8762/eureka/ zone2: http://localhost:8763/eureka/,http://localhost:8764/eureka/ availability-zones: region-east: zone1,zone2
application-zone2.yml:
server: port: 10002 eureka: instance: metadataMap.zone: zone2 client: register-with-eureka: true fetch-registry: true region: region-east service-url: zone1: http://localhost:8761/eureka/,http://localhost:8762/eureka/ zone2: http://localhost:8763/eureka/,http://localhost:8764/eureka/ availability-zones: region-east: zone1,zone2
3.4. Start the zuul gateway project. There are two examples to execute the command:
mvn spring-boot:run -Dspring.profiles.active=zone1 mvn spring-boot:run -Dspring.profiles.active=zone2
Verify Zone Affinity, access: localhost:10001/client/actuator/env, result:
Visit: localhost:10002/client/actuator/env, results:
You can see that the request gateway/client/actuator/env accesses the / actuator/env interface of the eureka client instance, the active Profiles returned by Gateway in zone 1 are zone 1, and the active Profiles returned by Gateway in zone 2 are zone 2.