First, the overall process:
1. service provider starts, it will write its own metadata information to the registry, and it will subscribe to configure metadata information;
2. When consumers start, it will write its own metadata information to the registry, and subscribe to a service provider, routing and configuration metadata information;
3. Service control center to start, will also subscribe to all consumers, service providers, routing and configuration metadata information;
4. When there is a service provider to leave or join the new service provider, registry service provider directory will change, the dynamic change notification information back to the consumer, the service control center
5. When a consumer initiates a service call placed, will be called asynchronously, statistical information reported to the monitoring center.
二、dubbo-admin
When dubbo framework service call, the user can (dubbo-admin) below to configure routing through the service management platform. If you want to change service parameters at runtime, users can dynamically configure below, the server will receive property changes through a subscription mechanism by service management platform (dubbo-admin), has been updated and re-exposed service
Third, the cache mechanism (source)
1. The cache file writes
2. The cache load
3. Cache preservation and renewal
4. retry mechanism
Fourth, design patterns
1. Templates
2. Factory