Skip to main content

10 posts tagged with "Announcements"

View All Tags

RabbitMQ 4.1 Performance Improvements

· 5 min read

RabbitMQ 4.1 is just around the corner 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:

  1. Lower and more stable memory usage for quorum queues
  2. Much better performance when consuming a long quorum queue
  3. Better performance for Websocket connections
  4. Lower memory usage and/or higher throughput for TCP connections

RabbitMQ 4.1: New Kubernetes Peer Discovery Mechanism

· 5 min read

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.

Package Repository Updates

· 2 min read

Team RabbitMQ has two updates related to our Debian and RPM repositories:

  1. On August 18, 2024, Team RabbitMQ's PackageCloud account will be discontinued
  2. Cloudsmith mirror repositories now use *.rabbitmq.com domains, please update your repository definition files

RabbitMQ 3.13.0 Is Here!

· 5 min read

RabbitMQ 3.13 is now available with support for MQTTv5, stream filtering and significant improvements to classic queue performance, especially for larger messages.

Read dedicated blog posts for more details about these changes:

RabbitMQ 3.13 is the final minor release in the 3.x series. The next release will be 4.0!

RabbitMQ Deprecation Announcements for 4.0

· 4 min read

In RabbitMQ 4.0, we intend to remove some RabbitMQ features to:

  • Increase the resiliency of the core broker
  • Decrease the number of suboptimal configurations available
  • Remove technical surface area (maintaining old code) from the team
  • Reduce the support burden

We continually innovate to meet and exceed our users’ expectations. Removal of older functionality that no longer meets these expectations, or serves our users, means we can focus on our mission to provide a stable, performant, and flexible messaging system.