Chapter 1. Features

The features added in this release, and that were not in previous releases of the AMQ broker, are outlined below.

Failover: Brokers can be fully redundant, allowing a backup broker to take over connections from a primary broker in the event of a failure. Optionally, a shared volume can be configured between the primary and backup broker.
Delivery guarantee: Some messages that a developer sends from his application require a guarantee of delivery guaranteeing that messages get from the application sending them to the application consuming and processing them. If a network link goes down or the broker experiences a power outage while the message is in transit the message broker must resend undelivered messages once it returns online or the network connection is restored.
Zero persistence: Brokers can be configured to not persist any messages for scenarios in which no guarantee is required, but high performance is.

Basic authentication: Brokers can authenticate clients using basic username and password credentials.
Role-based authentication: Brokers can authenticate and authorize clients to specific queues or message addresses based on roles assigned to the client.
SSL-encrypted connections: Connections between clients and broker or a broker and another broker are secure and utilize SSL to encrypt the connections.
Certificate-based authentication: Brokers can authenticate a client connection or a connection from another broker using certificates.

Dead connection detection: Brokers can detect dead connections when a client has exceeded specific lifespan that can be set either on the client’s connection factory or globally on the server.
Slow consumer detection: Brokers can detect slow consumers and disconnect them from the server when this feature is enabled.

Refer to the ActiveMQ Artemis project for additional information: http://activemq.apache.org/artemis/index.html