. NET enterprise-level application architecture design series of Application Servers

Here we will talk about application servers in a three-tier architecture. For e-commerce websites, mature architectures are basically hierarchical. The layered structure is suitable for the human brain's way of thinking, and is very effective in solving scalability. Currently, major solution providers in the market have Corresponding Hierarchical solutions in e-commerce and general WEB application fields. There is almost no dispute over software architecture design.

 

For the sake of scalability and maintainability, the application server is obtained by decoupling the business logic. This situation is very common in software systems and can be achieved through an additional layer of flexibility in any situation,PossiblePotential performance problems will be introduced. Before the advent of Windows Server 2008, the. NET platform did not have any special products for application servers. There are multiple optional solutions for setting up application servers. Common. NET application server solutions include:
A) use IIS to resident ASP. NET Web Service
B) use. NET Remoting to provide remote objects
C) Use Enterprise Services (COM +) to provide cross-process object calls

Among the three methods, the. NET Remoting using TCP/Binary channel is the best among the three solutions, while ASP. NET Web Service can provide more cross-platform features. In terms of performance comparison, ASP. NET Web Service is about TCP/Binary. about 60% of NET Remoting (related to transmitted data). The difference lies in ASP. NET Web Service will spend a lot of time on Serialization of large objects. The Remoting implementation in the binary format also provides support for Object-level (including single-piece -- singleton features), which is widely used in performance-demanding solutions.

In this case, the best solution isImplementationA more flexible architecture is provided to adjust policies at any time to minimize the cost of adjustment. That is to say, the core logic of the system is implemented as an object group, and then the facet method is used to adapt to different calling interfaces with minimal effort. Of course, it was initially in the form of SOAPublish WEB ServicesCall the client to implement a portable environment as much as possible. If this mode becomes a performance bottleneck in the system, it is changed to the TCP/Binary. NET Remoting mode.Release object.

In general, the architecture of the application server is an evolutionary model that can implement a smooth transition with changes in demand and actual load. When the application server's horizontal expansion cannot cope with larger loads, the actual performance bottleneck has been transferred to other places in the system, such as disk access or access bandwidth.