Dubbo Tour-Demand

in the previous article, we focused on Dubbo's architectural roadmap and had a simpler impression and understanding of it, while the basic requirements for Dubbo were the next .

before a large-scale service, the application may simply expose and reference remote services through tools such as RMI or Hessian, call through the URL address of the configuration service, and load balance through hardware such as F5.

For F5 hardware refer to F5 Networks

(1) with more and more services, service URL configuration management becomes very difficult, and the F5 hardware load Balancer's single point of pressure is getting bigger. At this point, a service registry, dynamic registration and discovery services are required to make the location of the service transparent. It also reduces the reliance on the F5 hardware load balancer by obtaining a list of service provider addresses in the consumer, which can reduce the partial cost.

(2) When further development, inter-service dependencies become a complex, even unclear which application to start before which application, the architect can not fully describe the application's architectural relationship. At this point, you need to automatically draw a dependency graph between applications to help the architect clean up the relationship.

(3) Then, the service is more and more calls, the capacity of the service problem is exposed, how much machine support this service needs? When should I add a machine?

In order to solve these problems,

The first step is to count the number of calls and response times for the service now, as a reference for capacity planning.

Secondly, to be able to dynamically adjust the weight, on-line, the weight of a machine has been increased, and in the process of increasing the time to record the change in response times, until the response time to reach the threshold, record the amount of traffic at this time, and then the amount of this traffic multiplied by the number of machines to push back total capacity.

      is aDubboof service governance,you just need to take a look at this chart first ..and so on the subsequent re-ZookeeperRegistration Center andDubboMonitoring Center for sharing,then come back and look at this picture .,It 's going to be better than this time ..

After understanding The basic needs of Dubbo , the next article needs to Dubbo The internal logic and invocation of the schema are explained next .

Dubbo Tour-Demand