Dubbo Communication (Resource Scheduling and Governance center)

Dubbo Communication (Resource Scheduling and Governance center)
1. What is Dubbo
With the development of the Internet, the scale of website application is expanding, the conventional vertical application architecture cannot be solved, the distributed service architecture and the mobile computing architecture are imperative, and a governance system is urgently needed to ensure an orderly evolution of the architecture.

2: The Evolution of architecture
1: Single Application architecture
When site traffic is small, you need only one app to deploy all the features together to reduce deployment nodes and costs. At this point, the data Access Framework (ORM) is the key to simplifying the effort of adding and deleting changes.
2: Vertical Application Architecture
As traffic increases, a single application increases the acceleration of the machine, and the application is split into several unrelated applications to improve efficiency. At this point, the web Framework (MVC) used to accelerate the development of front-end pages is critical.
3: Distributed Service architecture
When the vertical application is more and more, the interaction between applications is unavoidable, the core business is extracted, as an independent service, gradually formed a stable service center, so that the front-end application can respond to the changing market demand more quickly, at this time, to improve the business reuse and integration of the Distributed Service Framework (RPC) is the key.
4: Flow Computing Architecture
When the service is more and more, the evaluation of capacity, and the waste of small service resources appear gradually, it is necessary to add a dispatch center to manage cluster capacity and improve cluster utilization based on access pressure.
At this point, the resource Scheduling and Governance Center (SOA) that is used to improve machine utilization is critical.
5:dubbo
Dubbo is the management tool of the resource scheduling and governance center.
Architecture of the 3:dubbo

1: 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: Count the number of calls to the service and the Monitoring center of the call time.
Container: The service runs the container.
2: 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.