Chapter 1. Overview
AMQ .NET is a lightweight AMQP 1.0 library for the .NET Framework. It enables you to write .NET applications that send and receive AMQP messages.
AMQ .NET is part of AMQ Clients, a suite of messaging libraries supporting multiple languages and platforms. For an overview of the clients, see AMQ Clients Overview. For information about this release, see AMQ Clients 2.6 Release Notes.
1.1. Key features
- SSL/TLS for secure communication
- Flexible SASL authentication
- Seamless conversion between AMQP and native data types
- Access to all the features and capabilities of AMQP 1.0
- 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:
1.3. Supported configurations
AMQ .NET supports the following OS and language versions:
- Red Hat Enterprise Linux 7 with .NET Core 2.1
- Microsoft Windows 10 Pro with .NET Core 2.1 or .NET Framework 4.5
- Microsoft Windows Server 2012 R2 and 2016 with .NET Core 2.1 or .NET Framework 4.5
AMQ .NET is supported in combination with the following AMQ components and versions:
- All versions of AMQ Broker
- All versions of AMQ Interconnect
- All versions of AMQ Online
- A-MQ 6 versions 6.2.1 and higher
For more information, see Red Hat AMQ 7 Supported Configurations.
1.4. Terms and concepts
This section introduces the core API entities and describes how they operate together.
Table 1.1. API terms
A channel for communication between two peers on a network
A context for sending and receiving messages
A channel for sending messages to a target
A channel for receiving messages from a source
A named point of origin for messages
A named destination for messages
A mutable holder of application data
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.