We are delighted to announce support for AMQP 1.0 over WebSocket in VMware Tanzu RabbitMQ 4.1.
This feature enables any browser-based application to communicate with RabbitMQ using AMQP 1.0, paving the way for a wide range of efficient browser-based business messaging scenarios.
RabbitMQ 4.1.0 is
a new minor release that includes multiple performance improvements,
and a number of features such as thew new peer discovery mechanism for Kubernetes.
See Compatibility Notes below to learn about breaking or potentially breaking changes in this release.
Some key improvements in this release are listed below.
Quorum queue log reads are now offloaded to channels (sessions, connections).
In practical terms this means improved consumer throughput, lower interference of publishers on queue delivery rate to consumers, and improved CPU core utilization by each quorum queue (assuming there are enough cores available to the node).
Support for the properties and application-properties filters of AMQP Filter Expressions Version 1.0 Working Draft 09.
As described in the AMQP 1.0 Filter Expressions blog post, this feature enables multiple concurrent clients each consuming only a subset of messages from a stream while maintaining message order.
Graduated (mandatory) feature flags several minors ago has proven that they could use some user experience improvements. For example, certain required feature flags will now be enabled on node boot when all nodes in the cluster support them.
See core server changes below as well as the GitHub project dedicated to feature flags improvements for the complete list of related changes.
rabbitmqadmin v2 is a major revision of the
original CLI client for the RabbitMQ HTTP API.
It supports a much broader set of operations, including health checks, operations
on federation upstreams, shovels, transformations of exported definitions,
(some) Tanzu RabbitMQ HTTP API endpoints, --long-option and subcommand inference in interactive mode,
and more.
RabbitMQ 4.1 is around the corner (update: has been released) and, as usual, apart from new features, we have made some internal changes that should provide better performance.
There are at least 4 notable changes:
RabbitMQ 4.1 includes a completely redesigned peer discovery plugin for Kubernetes.
No configuration changes should be needed when upgrading to 4.1, so if you want,
you can just stop reading here. If you are interested in the details, read on.
This blog post explains the peer discovery subsystem in general
and the changes to rabbitmq_peer_discovery_k8s in particular.
RabbitMQ 4.1 introduces an exciting new feature: AMQP filter expressions for streams.
This feature enables RabbitMQ to support multiple concurrent clients, each consuming only a specific subset of messages while preserving message order. Additionally, it minimizes network traffic between RabbitMQ and its clients by dispatching only the messages that match the clients' interests.
In this blog post, we’ll explore what AMQP filter expressions are and walk through a simple Java example of how to use them.