Comparison and benefits of existing distributed technologies (sockets,. NET remoting, ASP. WebService, WSE, ES) and WCF

1:socket VS Remoting

Using a socket is undoubtedly the most efficient. However, in the complex interface environment, socket development efficiency is also the lowest. Therefore, in the case of development efficiency, remoting can be used instead of socket development. And:
1, the remoting speed of the TCP channel is very fast.
You can see through the Port View tool, remoting than the direct socket transmission content, should belong to the same order of magnitude. My other concern is that in the case of large clients, the remoting transmission efficiency will not be very low, the results after field testing, while the data communication to 300 clients, there is no loss of information.
2, although it is remote, but very close to the local call object.
That is, fully conform to object-oriented thinking.
3, can do to maintain the state of the object
Directly using the socket transmission mechanism, we must spend a lot of effort to deal with anomalies, broken nets, crashes and other phenomena, using remoting, these efforts will be greatly simplified.

2 Remoting vs WebService

1, WebService in the framework2.0 state can only be hosted in IIS and other application servers. Microsoft didn't offer ServiceHost to host WebService until 3.0, which greatly limited the flexibility of webservice in use. In a framework2.0 environment, if you have an application that is going to be out of IIS, you have to abandon webservice. (unless you want the code to implement a Web application server)
2, remoting can be hosted in your own code, you can also host in Windows Services and IIS. The greatest degree of flexibility in development and deployment is provided.
3, remoting when using the HTTP channel, also like WebService support through the route.
4, remoting and Websercie compared to provide two-way communication. Even hosting remoting in IIS is supported.
5, WebService Client Auto-generated proxy class is more complex. remoting, in general, is writing client code manually.
6, of course, WebService's main advantage is that it is an industry standard, and remoting is only Microsoft's own internal standards, if your application to leave the platform of Microsoft, you can only use WebService.

3:remoting vs WCF

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

4. Various comparisons of existing distributed technology performance

When migrating distributed applications written with ASP. NET Web services and. NET Remoting To WCF, the performance are at least comparable to the other existing Microsoft distributed communication technologies. In most cases, the performance are significantly better for WCF over the other existing technologies. Another important characteristic of WCF is, the throughput performance is inherently scalable from a uni processor to Quad processor.

To summarize the results, WCF is 25%-50% faster than ASP, and approximately 25% faster than. NET Remoting . Comparison with. NET Enterprise Service are load dependant, as in one case WCF was nearly 100% faster but in another SCE Nario it is nearly 25% slower (what?). For WSE 2.0/3.0 implementations, migrating them to WCF would obviously provide the most significant performance gains of Al Most 4x.

WebService Remoting WCF simple Speed comparisonA Performance Comparison of Windows communication Foundation (WCF) with Existing distributed communication technologie SThis is the authoritative point of MSDN:

When migrating distributed applications written with ASP. NET Web services and. NET Remoting To WCF, the performance are at least comparable to the other existing Microsoft distributed communication technologies. In most cases, the performance are significantly better for WCF over the other existing technologies. Another important characteristic of WCF is, the throughput performance is inherently scalable from a uni processor to Quad processor.

To summarize the results, WCF is 25%-50% faster than ASP, and approximately 25% faster than. NET Remoting . Comparison with. NET Enterprise Service are load dependant, as in one case WCF was nearly 100% faster but in another Scenari o It is nearly 25% slower. For WSE 2.0/3.0 implementations, migrating them to WCF would obviously provide the most significant performance gains of Al Most 4x.

WCF vs. Remoting (with DataSet)-performance comparison

DEBUGLZQ: According to the characteristics of the project, local conditions, realistic analysis of the needs of the project, select the most suitable technical framework.

Comparison and benefits of existing distributed technologies (sockets,. NET remoting, ASP. WebService, WSE, ES) and WCF