( 1 ) Dubbo works
The first layer: Service layer and the interface layer, to the service providers and consumers to achieve
The second layer: config layer disposed layer, mainly for dubbo various configurations
The third layer: Proxy layer (broken about washing), the service agent layer, a transparent generated client stub and a ticket service skeleton
The fourth layer: Registry registration and discovery layer (ruai think mouth blown), registered service layer, responsible for services
Fifth layer: Cluster layer (ct Lancaster), a cluster layer, a plurality of service providers package routing and load balancing, multiple service instances are combined into a
Sixth layer: Monitor layer (analog special), monitoring level, for rpc interface, the number of calls and call monitoring time
Seventh layer: Protocol layer (Reiter broken buckle), remote invocation layer, encapsulation rpc call
Eighth Layer: Exchange layer (competent thirst), the information exchange layer, encapsulating a request response mode, synchronous asynchronous transfer
Ninth layer: Transport layer (Laid-threading stripping), network transport layer, abstract mina and netty is uniform interface
Tenth layer: the serialize layer (from tome), a data sequence of layers
work process:
1 ) The first step, Provider to the registration center to register
2 ) The second step, consumer from the subscription service registration center, registration center will notify the consumer registered good service
3 ) The third step, Consumer call provider
4 ) The fourth step, Consumer and provider are asynchronous notification monitoring center
( 2 ) hung up the registry may continue to communicate it?
Yes, since the beginning of the initialization time, consumers will be the provider of address and other information pulled into the local cache, so the registry can continue to communicate hung up