Comparison of. NET Distributed Technologies

1. MSMQ (Microsoft Message Queue)

Microsoft Message Queuing is an asynchronous transfer mode that communicates with multiple different applications, which can be distributed on the same machine or in any location in the connected network space. The idea is that the sender of the message puts the information he wants to send into a container (what we call a message ) and then saves it to a message queue in a system's public space A local or offsite message receiver is then taken out of the queue to process messages sent to it.

With MSMQ (Microsoft Message Queue), application developers can easily communicate quickly and reliably with applications by sending and receiving messages. Message processing provides you with secure messaging and a reliable fail-safe method for performing many business processes.

MSMQ, like XML Web services and. Net remoting, is a distributed development technology. However, when using XML Web services or. Net Remoting components, the client needs to exchange information in real time with the server side, and the server needs to remain online. MSMQ can work offline while the server is temporarily saved in Message Queuing on the client side and then sent to server-side processing at a later time.

Obviously, MSMQ is not suitable for clients that require the server side to respond in a timely manner, and MSMQ interacts asynchronously with the server side without worrying about waiting for a lengthy process on the server side.

Although both XML Web services and. Net remoting provide the [OneWay] property to handle asynchronous calls, the server-side long method call is used to prevent long-time blocking of the client side. However, the problem of a large number of client workloads cannot be resolved, at which time the server accepts requests faster than processing requests.

Extended read: http://www.cnblogs.com/sk-net/archive/2011/11/25/2232341.html

Http://www.codeproject.com/Articles/193611/DotNetMQ-A-Complete-Message-Queue-System-for-NET

Extended keywords: Message queue messaging middleware

Thinking: Message queue OR Web Service

. NET Remoting

. Net Remoting technology, which we can consider as a distributed approach. As a mechanism for communication between applications,. Net remoting differs from MSMQ Message Queuing in that it does not support offline offline messaging and is only appropriate. NET platform. From the Microsoft product point of view, it can be said that Remoting is a distributed component of DCOM upgrade, it has improved a lot of features, and excellent integration into the. NET platform under the. NET Remoting Provides a framework that allows an object to interact with another object through an application domain. That's why we use Remoting. Why is it? In the Windows operating system, it is the separation of applications into separate processes. This process forms a boundary around the application code and data. If you do not adopt the interprocess communication IPC (Internet process Connection) mechanism, code executing in one process cannot access another process. This is an operating system protection mechanism for applications. In some cases, however, we need to cross the application domain and communicate with another application domain, that is, crossing the boundary (refer to MSDN).

There is no essential difference between the principles of . NET Remoting and Web Service implementations

The server sends a process number to the client, a program field number to determine the object's location.

. NET remoting and WebService are both frameworks used for communication, and their greatest advantage is that they can invoke remote objects like local objects, such as: Uploader Uploader = new Uploader () ; uploader. Save (file), you can use such a concise and abstract call implementation of the upload, do not have to do a series of socket processing, you can put more effort on business logic; the difference: 1, WebService is used in the Application Layer protocol HTTP encapsulation, so it can be called by many other languages, Many languages also implement the WebService proxy-side package and tools, as long as you know the WebService address (such as: http://www.baidu.com/SomeService.asmx), you can use, So webservice is easy to use, general, efficiency in general;. NET Remoting is encapsulated with the Transport Layer protocol TCP, so the data can be transmitted in binary, high efficiency;. NET Remoting Based on the. NET reflection mechanism, it is only convenient for. NET use (other language reflection mechanisms are implemented differently, some have no reflection at all); 2, webservice can cross the firewall, because the HTTP protocol is now widely used protocols, firewalls are generally not blocked, Does not say that WebService has a function through the firewall, 3, can only be used under the WinForm? If you are developing with. NET, any type of application can use. NET remoting with WebService, including Winform,asp.net, WPF, Silverlight ..., as long as you can using ... Can be used in their own Way 1). How does the. NET Remoting work?

Answer: The server sends a process number to the client, a program field number to determine the location of the object.

2) What is the difference between an XML Web service using ASMX and a. NET Remoting using soap?

Answer: TheWeb Service uses the messaging mechanism, while the Remoting uses the RPC. Web service can be used on different platforms, in different languages, remoting only for. Net. More efficient Remoting than XML Web Service

Web services are communicated as messages, messages are passed between the caller and the server, and. NET Remoting is object-based so that the methods of the object can be called across the network

3) Briefly discuss your understanding of the two technologies of remoting and WebService under the Microsoft. NET Framework and the practical applications.

Answer: WS is primarily available with HTTP, penetrating firewalls. and Remoting can use TCP/IP, binary delivery to improve efficiency.

4). Provides an overview of the understanding and practical application of remoting and WebService two technologies in. NET.

Answer: Remote logic call, Remoing interface can only be used in. Net

Remoting is a technique used in. NET to make method calls across machine, process, and AppDomain, and for a 30%-structured program, it can be built using remoting technology. It is the basic technology for distributed applications. Equivalent to previous DCOM

Web service is a common model for building applications and can be implemented on all operating systems that support Internet network communication. Web Service enables component-based development and the combination of the web to achieve the best, component-based object model.

Related recommendation: http://www.cnblogs.com/DebugLZQ/archive/2012/07/30/2614815.html

Https://msdn.microsoft.com/en-us/library/ms978420.aspx

Comparison of. NET Distributed Technologies