Basic understanding of service governance Eureka

1. In the traditional RPC remote calling framework, managing the dependency relationship between each service and service is more complicated, so service governance is needed to manage the dependency between services and services

Can achieve service invocation, load balancing, fault tolerance, etc., to achieve service discovery and registration

2. What is service registration and discovery

Eureka adopts the design architecture of CS. Eureka Server serves as the server for the service registration function. It is the service registration center. And other microservices in the system,

Clients using Eureka connect to Eureka Server and maintain a heartbeat connection. In this way, the maintenance personnel of the system can use the Eureka Server to monitor the normal operation of each microservice in the system.

In service registration and discovery, there is a registration center. When the server starts, it will communicate the current server information such as service address

The address, etc., is registered to the registration center as an alias. The other party (consumer | service provider) uses the alias to go to the registration center to obtain the actual

Service communication address, and then implement the local RPC call RPC remote call framework core design idea: lies in the registration center, because the use of registration center management

A dependency relationship between each service and service (service governance concept). In any RPC remote framework, there will be a registration center (storage service address related information (interface address))

Eureka system architecture

Dubbo architecture

Two components of Eureka

Just like my previous payment module and consumer module are registered in the service registration center, when the consumer calls the payment module api, the service communication address will be obtained from the registration center

Then call the RPC remote call locally to call the interface