First, what is dubbo
Dubbo is a high performance, open source lightweight RPC framework , providing high performance and transparency of RPC remote service call solutions, SOA service governance plan (the interface for remote method invocation, intelligent fault tolerance and load balancing, and service automatic discovery and registration functions). Simply put, dubbo is a service framework, only when distributed, have dubbo demand for such a distributed service framework, and is essentially a service call, saying that white is distributed framework for remote service invocation. Farewell Web Service mode wsdl, to service providers and consumers Register on dubbo).
Second, what is RPC
RPC [ Remote Procedure Call] refers to the Remote Procedure Call, it is an interprocess communication, thinking he is a technique, not the norm. It allows a program to call another address space (typically on another machine sharing network) procedure or function, rather than the programmer explicitly coding details remote calls. That programmer whether to call a local or remote function, essentially calling code written in basically the same.
RPC two core modules: communication, serialization.
The basic principle of RPC:
Third, the basic concept
Service Provider ( Provider ) : exposed services service provider, a service provider at the start, registration services they provided to the registry.
Service consumers ( Consumer ) : call the remote service consumer services, consumer services at startup, subscribe to the registry services they need, service consumers, providers from the list of addresses, soft load balancing algorithm based on the election a provider of call, if the call fails, then select another call.
Registry ( Registry ) : Returns the registry service provider address list to the consumer, if there is a change, the registry will be based on long push to change the data connection to the consumer.
Monitoring Center ( Monitor ) : service consumers and providers, in memory of the cumulative number of calls and call time, time sent once per minute statistical data to the monitoring center.
Call relationship Description:
Responsible for starting the service container, load, run service provider.
Service provider when you start, registration services they provided to the registry.
Consumer services at startup, you need to subscribe to the service registry.
Registry return address list service providers to consumers, if there is a change, the registry will be based on long push to change the data connection to the consumer.
Service consumers, providers from the list of addresses, soft load balancing algorithm, choose a provider call, if the call fails, then select another call.
Service consumers and providers, in memory of the cumulative number of calls and call time, time sent once per minute statistical data to the monitoring center.