Introduction
Message Queuing is a messaging infrastructure and a development tool for creating distributed, loosely-coupled, messaging applications for the Windows 2000 operating system or later.
Message Queuing Applications send messages to queues, which are temporary storage locations used to ensure that messages reach their destination. These applications are also called in the industry as message-queuing software, store-and-forward software, or message-oriented middleware.
Advantages of Message Queuing:
Message Queuing provides guaranteed message delivery, efficient routing, security, transactional support, and priority-based messaging.
With Message Queuing, end users can communicate across networks and computers that may be offline, irrespective of the current state of the network and computers.
System administrators can use Message Queuing to efficiently manage large, complex networks of computers and message queues.
MIS decision makers get more reliable communication and more efficient use of network resources.
Developers can focus on business logic instead of networking issues, because Message Queuing effectively provides guaranteed network communication.
Message Queuing is of particular interest to system administrators for installing and managing the infrastructure
Message Queuing VS E-Mail
Differences:
Message Queuing moves data between applications, using a system of queues distributed on various computers.In contrast, e-mail is an application that enables communication between people. For example, Microsoft Exchange Server moves e-mail messages between Exchange users, using a central post office and mail folders.
The Message Queuing sender and recipient is an application, whereas an e-mail sender and recipient is generally a person.
A Message Queuing message body is generally binary data, typically understood only by applications that process the message. An e-mail message body is generally formatted text, understood by any person who reads it.
A Message Queuing application does not need a computer to be online to send messages. E-mail typically needs a connection to a server or post office to send e-mail.
Message Queuing is optimized to provide extremely fast communication throughput in comparison with e-mail applications.
Message Queuing provides message prioritization, guaranteed message delivery, and acknowledgment of messages.
Message Queuing provides options for memory-based, disk-based, or transactional delivery of messages.
Similarities:
Both the technologies don’t require recipients to be present at the time messages are sent to them. Both technologies store messages and then forward them when the recipient is available.
Both types of messages indicate the address of the sender and the receiver.
Message Queuing and .NET
The System.Messaging namespace provides classes that allow you to connect to, monitor, and administer message queues on the network and send, receive messages.
MessageQueue Class provides access to a queue on a Message Queuing server. SEND method enables your application to write messages to the queue. RECEIVE method receives the first message in the queue, removing it from the queue.
Message Class Provides access to the properties needed to define a Message Queuing message. It has properties such as SenderId, MessageType, Body,Priority, SourceMachine, DestinationQueue etc.
Conclusion:
Message Queuing Component can be use along with the other applications created in .NET to provide inter-process, intra-net, enterprise-wide implementations.
|
No responses found. Be the first to respond and make money from revenue sharing program.
|