DUBBO distributed RPC remote call thinking

dubbo there are two concepts, one is to provide the service side, a consumer side, we also called service providers, and consumers.

Zookeeper is dubbo service center, service first side to write the true meaning of the interfaces and VO objects labeled jar package, to provide consumers rely on,

After writing the true realization of our need to register to zookeeper service center, then register the corresponding consumer connection zookeeper address references related to the interface,

This is the use dubbo and zeekeeper simple process, and the benefits of using dubbo zookeeper: for example we have the pc, APP server,

Background and red envelope systems require the user's query and each query will open a database connection code works and there will be repeated,

We need to be optimized and, if different modules developed separately in different ways to achieve the realization of logic lead to inconsistent results.

So that we can use dubbo provide services, it can be used between the various modules, direct manipulation interface rather than a service API.

Guess you like

Origin www.cnblogs.com/KFKang/p/12037593.html