Comparison and advantages of existing distributed technologies (socket,. Net remoting, Asp.net WebService, WSE, ES) and WCF

Document directory

• 4. Comparison of performance of existing distributed Technologies

1: Socket vs remoting

Using socket is undoubtedly the most efficient. However, in a complex interface environment, the socket development efficiency is also the lowest. Therefore, with both development efficiency, remoting can be used instead of socket development. And:
1. The remoting speed of the TCP channel is very fast.
You can use the port viewing tool to find that the content transmitted by remoting is the same order of magnitude than that transmitted by direct socket. My other concern is whether the remoting transmission efficiency will be very low in the case of a large number of clients. The result is tested on the site and the data communication is performed on 300 clients, so there is no information loss.
2. Although it is remote, It is very close to the local call object.
That is, it fully complies with the object-oriented ideology.
3. The object state can be maintained.
Directly Using the socket transmission mechanism requires a lot of effort to handle exceptions, network disconnection, and crashes. Using remoting will greatly simplify this process.

2 remoting vs WebService

1. In framework2.0 status, WebService can only host on application servers such as IIS. Microsoft didn't provide servicehost to host WebService until 3.0, which greatly limits the flexibility of WebService in use. In framework2.0, if an application exists without IIS, You have to discard WebService. (Unless you want code to implement a Web application server)
2. remoting can be hosted in your own code, Windows Services, and IIS. It maximizes the flexibility of development and deployment.
3. When using the HTTP channel, remoting also supports penetration routing like WebService.
4. remoting provides two-way communication compared with websercie. It is supported even if you host remoting in IIS.
5. The proxy class automatically generated by the WebService client is complicated. Remoting generally writes client code manually.
6. Of course, the main advantage of WebService is that it is an industry standard, while remoting is only an internal standard of Microsoft. If your application is to break away from Microsoft's platform, you can only use WebService.

3: remoting vs WCF

Compared with WCF, it is more about the popularity of the platform. In the current environment, the popularity of 2.0 is still the highest. If 3.0 or even 4.0 of the day is popular, of course, WCF is the best.

4. Comparison of performance of existing distributed Technologies

When migrating distributed applications written with ASP. net web services, WSE ,. NET Enterprise Services and. net remoting to WCF, the performance is at least comparable to the other existing Microsoft Distributed communication technologies. in most cases, the performance is significantly better for WCF over the other existing technologies. another important characteristic of WCF is that the throughput performance is inherently scalable from a uni processor to Quad processor.

To summarize the results, WCF is 25%-50% faster than ASP. NET Web Services, and approximately 25% faster. net remoting. comparison. NET Enterprise Service is load dependant, as in one case WCF is nearly 100% fasterBut in another scenario it is nearly 25% slower (Why ?). For WSE 2.0/3.0 implementations, migrating them to WCF will obviusly provide the most significant performance gains of almost 4x.

WebService remoting WCF simple speed comparison a performance comparison of Windows Communication Foundation (WCF) with existing distributed communication technologies This is an authoritative point of msdn:

When migrating distributed applications written with ASP. net web services, WSE ,. NET Enterprise Services and. net remoting to WCF, the performance is at least comparable to the other existing Microsoft Distributed communication technologies. in most cases, the performance is significantly better for WCF over the other existing technologies. another important characteristic of WCF is that the throughput performance is inherently scalable from a uni processor to Quad processor.

To summarize the results, WCF is 25%-50% faster than ASP. NET Web Services, and approximately 25% faster. net remoting. comparison. NET Enterprise Service is load dependant, as in one case WCF is nearly 100% faster but in another scenario it is nearly 25% slower. for WSE 2.0/3.0 implementations, migrating them to WCF will obviusly provide the most significant performance gains of almost 4x.

WCF vs. remoting (with dataset)-Performance Comparison

 

Debuglzq: select the most appropriate technical architecture based on the characteristics of the project and the needs of the project based on local conditions and facts.

[Organize by yourself and use it for personal learning. Do not spray it ~ Do not see me or not ~]