Distributed typically deals with large traffic volumes, increasing access speed and traffic by distributing requests to multiple machines or services
The following is the configuration of most servers now
650) this.width=650; "src=" http://s5.51cto.com/wyfs02/M01/80/2D/wKioL1c6k7vw0lMKAAJVaP9OQPk440.jpg "title=" RV ' p1{ rkvsjro4}9[) @XJR2. jpg "alt=" wkiol1c6k7vw0lmkaajvap9oqpk440.jpg "/>
We say from the bottom up:
code layer , which is usually configured with some architecture, can configure the maximum number of connections, file upload size, user login information retention time and so on, in addition to the architecture itself will involve some design patterns, object creation, preservation, Code business logic optimization. These all affect the speed and concurrency of the program processing requests.
If the request is very slow, and obviously familiar with the card in this place, you can consider optimizing the code, of course, if the database pressure is too large, it will be distributed to the database and other ways of optimization, here for the time being not detailed acceptance, follow-up will be on the database distributed.
container layer : More commonly used have tomcat,jetty, they are the code to run the container, with Tomcat for example, Tomcat can configure the maximum number of threads for the requested amount, each thread can process a request,
<connector port= "8080" maxthreads= "75" minsparethreads= "maxsparethreads=" Enablelookups= "false" redirectport= "8443" acceptcount= "debug=" 0 "connectiontimeout=" 20000 " Disableuploadtimeout= "true"/>
The number of threads is a critical configuration for Tomcat to handle the maximum number of requests, and of course the large and impossible configuration of threads is unrealistic, although it does not itself limit the maximum number of threads, but it is limited by hardware, operating system, and container versions, depending on the situation
It is easy to have a maximum waiting queue number, which also has an impact on the maximum number of requests.
Server Architecture Configuration
650) this.width=650; "src=" http://s1.51cto.com/wyfs02/M00/80/2D/wKioL1c6mfzwDAsiAAKJylJT01c515.jpg "title=" w0g[ 7e0%$[l1ih0w) y_~c[v.jpg "alt=" Wkiol1c6mfzwdasiaakjyljt01c515.jpg "/>
Dubbo Schema Description
650) this.width=650; "src=" http://s1.51cto.com/wyfs02/M01/80/2D/wKioL1c6mlLw5jGtAADS_d20SxE622.jpg "title=" Wk%pzy }4ibtidqtz8$$4 (h4.jpg "width=" 593 "height=" 527 "border=" 1 "hspace=" 1 "vspace=" 1 "style=" WIDTH:593PX;HEIGHT:527PX; " alt= "Wkiol1c6mllw5jgtaads_d20sxe622.jpg"/>
Web site Distributed Architecture _1_ Brief