Yesterday, I chatted with Yu Yi, Li Guiping, and a few colleagues, chatting with the next generation community cluster extension, and later I thought about one night, I think the next generation of community processing clusters have three ways:
First of all, it is clear that under small users, perhaps the following cluster thoughts will make the program performance, but under small users, although the performance is poor, the user experience is not bad. Under a large number, performance is good, and the user experience is not bad. What we have to pursue is whether the user experience is good regardless of the size of the size, not the performance.
Next generation community, if you find that a single server can no longer increase performance (cost too high, unacceptable), you can improve the user experience by adding the server, by increasing the server. You need not to modify the code, you only need to pass the configuration:
1, pure technical distribution. Using Microsoft WIN load balancing, the average distribution of web layer servers; uses Microsoft COM (enterprise development) distributed function, allocal intermediate layer business logic and cache; use Microsoft Database Cluster ideology, power stress of database server; Concept, enhance the performance of the static content server, as well as diversion to different servers.
2, remove each function module, each functional module is loosely coupled, and the idea of SOA and AOP. Web section, short message, bamboo management, and ordinary forums These function modules can be deployed on different servers, each server is completed. The various services are loosely coupled. The intermediate layer is also a web layer, and is also split into a different application domain according to the function. On the database, it also splits to different databases according to the function. Static content can also be split according to function.
3, split the forum, each forum is a separate part. For example, we can use the Web layer, intermediate layer, static file layer, and database layer of the .NET community, and the content of other communities will not affect them. We can also separate the web layers, VC and VB, while intermediate layers Vc and Vb are used and used, and the static file layer and the database layer are also used. Through this flexible way, it is convenient to increase the user experience of the entire system by adding the server.
Note that this method of splitting the forum can sufficiently utilize the existing old machine, which is the largest extensibility. In the previous two clusters, in fact, their scalability, there is certainly limited, and there is no limitation, and the third method can be expanded without limitation. The next generation community should support clusters of the above three ways. You don't need to modify the code, you can improve the user experience in an increase in the machine.
