Enterprise applications, how the services of a (project architecture evolution)

1. Evolution of Enterprise Application Architecture

　　1.1. Figure architecture evolution

 

　　1.2. Text description

# Single application architecture 
    when website traffic is small, only one application, all functions are deployed together to reduce the cost of deployment and node 

# vertical application architecture 
    when traffic is gradually increasing, a single application acceleration caused by increased machine increasingly the smaller, the application is split into several disparate applications to enhance the efficiency of 

# distributed service architecture 
    when more and more vertical applications, the inevitable interaction between applications, will be drawn out of the core business, as an independent service, gradually to form a stable service center, the front-end applications to more quickly respond to changing market demands 

Circulating computing architecture 
    when more and more services, capacity assessment, waste of resources and other small service issues is gradually emerging, this time to be adding a scheduling Center-based access to real-time pressure management cluster capacity, improve the utilization of cluster 
    
# entire evolutionary path of understanding: 
    a single node application -> application clusters -> distributed applications -> services management

 

2. Service Management Solutions

# 1 Small-scale service solutions 
    through RMI or hessian tools, simple exposure and reference the remote service, call the service by configuring the url to 

# 2 . Large-scale service solutions 
    # 2.1 . Demand 
        a. If the service more more configuration management service url becomes very difficult. At this point, you need a service registry, dynamic registration and discovery services 
        b. If the dependencies between services complex, even difficult to sort out the order to start between applications. At this point, you need a service automatically manage 
        c. If the service call volume increasing, how to assess the capacity of the service? How many machines need? At this point, we need a service capacity planning and management 
    # 2.2 solutions. 
        Service Governance Framework: dubbo, spring cloud