RabbitMQ 3.7.27 releases: open source message broker

by · Published · Updated

RabbitMQ is the most popular open source message broker.

RabbitMQ is lightweight and easy to deploy on-premises and in the cloud. It supports multiple messaging protocols. RabbitMQ can be deployed in distributed and federated configurations to meet high-scale, high-availability requirements.

RabbitMQ runs on many operating systems and cloud environments and provides a wide range of developer tools for most popular languages.

Feature

Asynchronous Messaging

Supports multiple messaging protocols, message queuing, delivery acknowledgement, flexible routing to queues, multiple exchange type.

Developer Experience

Deploy with BOSH, Chef, Docker and Puppet. Develop cross-language messaging with favorite programming languages such as: Java, .NET, PHP, Python, JavaScript, Ruby, Go, and many others.

Distributed Deployment

Deploy as clusters for high availability and throughput; federate across multiple availability zones and regions.

Enterprise & Cloud Ready

Pluggable authentication, authorization, supports TLS and LDAP. Lightweight and easy to deploy in public and private clouds.

Tools & Plugins

Diverse array of tools and pluginssupporting continuous integration, operational metrics, and integration to other enterprise systems. Flexible plug-in approach for extending RabbitMQ functionality.

Management & Monitoring

HTTP-API, command line tool, and UI for managing and monitoringRabbitMQ.

Changelog v3.7.27

Core Server

Enhancements

  • More peer discovery errors are retried.

    GitHub issue: rabbitmq/rabbitmq-server#1627

  • Initial Erlang/OTP 24 compatibility.

    Erlang/OTP 24 is expected to ship in mid-2021. While RabbitMQ 3.7 will be out of support by then,
    some initial compatibility work was backported to this branch due to contious integration on Erlang/OTP master.

Federation Plugin

Bug Fixes

  • One-off connections periodically used by exchange federation links now handle timeouts in certain
    operations gracefully. This avoids unnecessary link disruption and restarts in certain environments.
    The default interval has also been bumped from 30s to 90s.

    In environments with stable topologies the interval can be significantly increased to decrease connection
    churn, simplify monitoring and in general conserve some resources:

    %% advanced.config
[
 {rabbitmq_federation, [
     %% 86400 seconds or 24 hours
     {internal_exchange_check_interval, 86400000}
 ]}
].

    GitHub issue: rabbitmq/rabbitmq-federation#107

Download

Tags: