Four, Spring Cloud eureka--Introduction

Spring Cloud Eureka is part of the spring cloud Netflix MicroServices Suite, which has two footprints based on Netflix Eureka and is primarily responsible for service governance capabilities in the MicroServices architecture. Spring Cloud adds spring boot-style automation to Eureka, and we only need to easily integrate the MicroServices applications built with spring boot by simply introducing dependency and annotation configurations into the Eureka Service governance system.

Spring Cloud Eureka, using Netflix Eureka for service registration and discovery, contains both server-side components and client-side components, and both the server and the client are written in Java. So Eureka is primarily suitable for distributed systems implemented through Java, or for systems built with JVM-compatible languages. However, because the service governance mechanism of the Eureka Server provides a complete restful API, it also supports the inclusion of non-Java language-built microservices applications in the Eureka Service governance system. Only when using other language platform, you need to implement Eureka client program. Fortunately, however, in several of the more popular development platforms, there have been some client implementation frameworks for the Eureka Registry, such as. NET platform Steeltoe, node. js, Eureka-js-client, and so on.

Eureka Server, we are also known as the Service Registration center. Like other service registries, it supports highly available configurations. It relies on strong consistency to provide good service instance availability and can handle a variety of different failure scenarios. If Eureka is deployed in cluster mode, when there are shards in the cluster failing, then the Eureka goes into self-protection mode. It allows the discovery and registration of services to continue during a shard failure, and other shards in the cluster will synchronize their status back when the failed shard resumes running

Eureka Client, mainly handles the registration and discovery of services. The client service is embedded in the code of the client application through annotations and parameter configuration, and when the application runs, the Eureka client registers its own service with the registry and periodically sends a heartbeat to update its service lease. At the same time, it can query the current registered service information from the server and cache them locally and periodically refresh the service state.

Four, Spring Cloud eureka--Introduction