Red Hat SummitChapter 1. Overview
AMQ .NET is a lightweight AMQP 1.0 library for the .NET Framework. It allows you to write client and server applications that send and receive AMQP messages.
AMQ .NET is part of AMQ Clients, a suite of messaging libraries supporting multiple languages and platforms. See Introducing Red Hat JBoss AMQ 7 for an overview of the clients and other AMQ components. See AMQ Clients 1.2 Release Notes for information about this release.
AMQ .NET is based on AMQP.Net Lite.
1.1. Key Features
AMQ .NET offers convenience for simple tasks while still providing a full set of messaging tools to build complex applications.
- Access to all the features and capabilities of AMQP 1.0
- SSL/TLS and SASL for secure communication
- Seamless conversion between AMQP and native data types
- An integrated development environment with full IntelliSense API documentation
1.2. Supported Standards and Protocols
AMQ .NET supports the following industry-recognized standards and network protocols.
- Version 1.0 of the Advanced Message Queueing Protocol (AMQP)
- Modern TCP with IPv6
1.3. Supported Configurations
AMQ .NET supports the following OS and language versions. See Red Hat JBoss AMQ 7 Supported Configurations for more information.
AMQ .NET is supported on Microsoft Windows Server 2012 R2 x86-64 with .NET Framework 4.5.
1.4. Terms and Concepts
This section introduces the core API entities and describes how they operate together.
| Entity | Description |
|---|---|
| Connection | A channel for communication between two peers on a network |
| Session | A serialized context for sending and receiving messages |
| Sender link | A channel for sending messages to a target |
| Receiver link | A channel for receiving messages from a source |
| Source | A named point of origin for messages |
| Target | A named destination for messages |
| Message | A mutable holder of application content |
AMQ .NET sends and receives messages. Messages are transferred between connected peers over links. Links are established over sessions. Sessions are established over connections.
A sending peer creates a sender link to send messages. The sender link has a target that identifies a queue or topic at the remote peer. A receiving client creates a receiver link to receive messages. The receiver link has a source that identifies a queue or topic at the remote peer.
