Architecture
(#)
Node role Description:
- Provider: The service provider that exposes the service.
- Consumer: invokes the service consumer of the remote service.
- Registry: Registration Center for service Registration and discovery.
- Monitor : The monitoring center of the call times of the statistics service and the call time.
- Container: The service runs the container.
Call Relationship Description:
- 0. The service container is responsible for starting, loading, and running the service provider.
- 1. Upon launch, the service provider registers its services with the registry.
- 2. When the service consumer starts, it subscribes to the registration center for the services it needs.
- 3. The registry returns the service provider address list to the consumer, and if there is a change, the registry will push the change data to the consumer based on a long connection.
- 4. Service consumers, from the provider address list, based on the soft load equalization algorithm, select a provider to make the call, if the call fails, then choose another call.
- 5. Service consumers and providers, the cumulative number of calls in memory and call time, timed to send statistics every minute to the monitoring center.
(1) Connectivity:
- Registries are responsible for registering and locating service addresses, equivalent to directory services, where service providers and consumers interact with the registry only at startup, and the registry does not forward requests and is less stressful
- Monitoring Center is responsible for statistics of the number of service calls, call time, etc., statistics are first sent to the Monitoring center server every minute after the memory summary, and the report shows
- The service provider registers its services with the registry and reports the call time to the Monitoring center, which does not include network overhead
- The service consumer obtains the service provider address list from the registry and invokes the provider directly based on the load algorithm, reporting the call time to the Monitoring center, which includes the network overhead
- Registration Center, service provider, service consumers are long connections between the three, except the monitoring center
- The registry will immediately push events to inform consumers of the presence of a long-connected-aware service provider, service provider downtime
- The Registry and Monitoring Center are all down, without impacting the already running providers and consumers, who cache the provider list locally
- Registries and monitoring centers are optional and service consumers can connect directly to service providers
(2) Jian-like sex:
- Monitoring Center outage does not affect use, just lost part of the sampled data
- After the database is down, the registry can still provide a list of services through the cache, but cannot register for new services
- Registration center peer cluster, after any one outage, will automatically switch to another
- After the registry is all down, service providers and service consumers can still communicate via local cache
- Service provider stateless, any one outage, does not affect the use of
- After the service provider is all down, the service consumer app will not work and unlimited re-connect waits for the service provider to recover
(3) Flexibility:
- The registry is a peer cluster that dynamically increases the machine deployment instance, and all clients will automatically discover the new registry
- Service provider stateless, can dynamically increase the machine deployment instance, the registry will push the new service provider information to the consumer
(4) Upgrade:
- When the scale of service cluster expands further, it needs to realize dynamic deployment and flow calculation, and the existing distributed service architecture will not bring resistance:
- Deployer: The local agent for the automatic deployment service.
- Repository: The warehouse is used for storage service app release packages.
- Scheduler: The dispatch center automatically increases and decreases the service provider based on the access pressure.
- admin: Unified Management Console.
Preliminary knowledge of Dubbo series before 2-DUBBO architecture design
