We are pleased to announce that RabbitMQ 4.0 supports AMQP 1.0 as a core protocol, providing the following benefits:
Effective June 1st, the RabbitMQ community support and release policies will change for the open source distributions of RabbitMQ. The goal of these changes is to ensure that the RabbitMQ team has time to focus on developing new features for the Open Source and commercial versions of RabbitMQ.
Erlang/OTP 27.0 was released on May 20th, 2024. While it contains a lot of exciting features and improvements, unfortunately RabbitMQ currently doesn't work well with this version. We are aware of significant performance regressions, as high as 30% lower message throughput in many common workloads.
We are investigating the root cause of this regression. Please do not use Erlang/OTP 27 with RabbitMQ at this time.
We will announce support for Erlang/OTP 27 when we are confident that it works well with RabbitMQ.
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!
We've already announced two major new features of 3.13 in separate blog posts:
This post focuses on the changes to the classic queues in this release:
We have been working for several weeks on a new website for RabbitMQ. We plan to release this significant upgrade shortly after RabbitMQ 3.13.0 is released! At this point, we would love you to visit the new website and tell us what you think :-)
In this blog post, I will go over the reasons we are doing this and what improvements it will bring to you.
A previous post gave an introduction to stream filtering, a new and exciting feature in RabbitMQ 3.13. In this post we cover the internals of stream filtering. Knowing the design and implementation will help you to configure and use stream filtering in the most optimal way for your use cases.
Stream filtering is a new feature in RabbitMQ 3.13. It allows to save bandwidth between the broker and consuming applications when those applications need only a subset of the messages of a stream.
Keep reading to find out how stream filtering works and see it in action.
Native MQTT released in RabbitMQ 3.12 has delivered substantial scalability and performance improvements for IoT use cases.
RabbitMQ 3.13 will support MQTT 5.0 and will therefore be the next big step in our journey to make RabbitMQ one of the leading MQTT brokers.
This blog post explains how the new MQTT 5.0 features are used in RabbitMQ.
RabbitMQ 3.12 will be released soon with many new features and improvements.
This blog post focuses on the the performance-related differences.
The most important change is that the lazy mode for classic queues is now the standard behavior (more on this below).
The new implementation should be even more memory efficient
while proving higher throughput and lower latency than both lazy or non-lazy implementations did in earlier versions.
For even better performance, we highly recommend switching to classic queues version 2 (CQv2).
