Shulou(Shulou.com)06/02 Report--

This article mainly explains "what is the performance of WCF". The content of the explanation is simple and clear, and it is easy to learn and understand. Please follow the editor's train of thought to study and learn how the performance of WCF is.

With the development of the times, the WCF launched by Microsoft is used by more and more of us. We analyze the performance of WCF. It is a complex task to design, build, maintain and version control distributed applications. Security, reliability, transactional, and scalable factors and tasks become more complex. Because of the complexity of the problems, WCF is designed to solve these problems, and WCF is a very complex technology. In order to see WCF performance, I divided the main features into 10 categories: independent version control, asynchronous forward-only messaging, platform unity, security, reliability, transaction support, interoperability, performance, scalability, and configuration.

Independent version control

The application of system version control has become a headache. As I mentioned earlier, component-oriented design does not solve these problems well in distributed applications. If any technology is recognized in the distributed world, it must allow different parts of the distributed application to be versioned independently. Follow the WS-* specification, pay attention to the content of WS-* about message definition, and allow the called service to be developed at different rates. These features are not as important as the underlying principles for creating WCF applications, but I think they are the most important by-products of using WCF.

Asynchronous one-way message

Many of our applications use the request-response pattern to invoke functions. Typically, we call a function, wait for the result to return, and then execute based on the returned result. This approach is particularly common on Internet. Every time we request a page, we have to wait for a response from the page. Limited to our conditions, most distributed applications use a request-response approach. Although it may seem unnatural at first, asynchronous forward-only messaging is a more efficient way for task-distributed applications that cross IO boundaries. I think this is another benefit of using WCF. The asynchronous forward-only message mode allows the use of efficient processing resources and makes it easier to use the advanced functions, reliability and corresponding capabilities of distributed applications.

Platform unification

Many of the distributed technologies that Microsoft has released in the past; some have become important guiding technologies for the birth of WCF. And many technologies are still in use. For example, before the release of WCF, Microsoft supported five major distributed technologies: RPC, WSE, ASMX, Remoting, COM+, and MSMQ. In the past, the distributed technology of * * depended on the requirements of the application system. For example, if distributed applications are based on .NET Framework, then .NET Remoting is chosen because it is an efficient way to communicate between .NET Remoting applications. If an application needs guaranteed message transmission and persistence, then MSMQ is the choice. The two technologies have different API, programming methods, operation requirements and configuration requirements. As a result, the application code is tightly bound to these technologies, and these technologies are also bound to specific functions. Some new technologies allow us to combine features, such as transactional and queued COM+. This model works as long as the requirements do not change or do not use other unsupported ways.

What is needed for your application to communicate with other .NET Framework applications, non-.NET Framework applications, and transaction-enabled processing? Before WCF, there were no good choices, and in essence, these requirements led developers to either abandon a requirement or write their own communication technology. Compared with older technologies, WCF can integrate old technical features and unify them into a single programming model, as shown in Table 1-1.

Table 1-1 WCF feature comparison

Feature

WSE

ASMX

Remoting

COM+

MSMQ

WCF

WS-* support

X

X

X

Basic Web service interoperability

X

X

X

.net-to-.NET communication

X

X

Distributed transactions

X

X

X

Queued messaging

X

X

Objectively speaking, WCF performance does not provide us with the features of unconstrained connections, but it does provide us with more connectivity features than with.

Thank you for reading, the above is the content of "what is the performance of WCF". After the study of this article, I believe you have a deeper understanding of how the performance of WCF is, and the specific use needs to be verified in practice. Here is, the editor will push for you more related knowledge points of the article, welcome to follow!

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.