Today, we're pleased to announce that RabbitMQ 3.7.5 is now available on the Compose platform. This release also marks the start of a new new-release protocol we are introducing to help you manage your database upgrades.
The New Release Protocol
As you may know, we've had the ability to introduce new versions of databases but keep our "preferred" default version at an earlier version for some time. We're going to be making more use of this. For this update of RabbitMQ 3.7.5, we'll be putting the new version online without setting it to preferred. You can try it out and even clone your production systems onto a new deployment to give it a full test.
In seven days, we aim to flick the switch on RabbitMQ 3.7.5 and give it preferred status. It'll still be up to you when you upgrade your deployments though, eventually we'll look to remove older versions according to our database lifecycle policy.
When we introduce new database versions in future, our plan will be to make them available but not preferred and announce when they will become preferred.
One of the reasons for this change is to make life easier for users of Compose's APIs. If you are a user of the API, you'll know that creating a new database deployment is very simple and it automatically uses the current preferred version. Although it is possible to "pin" the required version in the API request, it isn't done that often. So we are adding a 7 day period between going live and going preferred to allow API users to pin versions or prepare for a new preferred version.
Back with our RabbitMQ update, many of the changes in RabbitMQ 3.7 are not user visible such as the new configuration formats, a peer discovery subsystem, a distributed management plugin and redesigned CLI tools. There's also been a lot of engineering around reliability and manageability. Five patch versions in, we're bringing 3.7.5 to the Compose platform.
At Compose, we've focussed on moving to the new configuration mechanisms for RabbitMQ 3.7. What we have added is support for the JMS Topic Exchange which joins the Delayed Message support in the Plugins view. The JMS Topic Exchange offers the server-side support needed for the RabbitMQ JMS Client.
Read more articles about Compose databases - use our Curated Collections Guide for articles on each database type. If you have any feedback about this or any other Compose article, drop the Compose Articles team a line at email@example.com. We're happy to hear from you.
attribution Gavin Allanwood