Couple of key public service announcements this month. First, the deadline for submitting a talk for RabbitMQ Summit 2019 (5 November in London UK) was May 10. We had a great line-up last year at the inaugural event and we’re looking forward to an even better event this fall.
Then, on May 23, we’ll be doing an overview of what’s new in RabbitMQ 3.8 (beta 4 of which has dropped recently). Whether you’re a couple versions behind, or on the latest 3.7.14 release, you’re going to want to learn about the latest features and changes.
Team RabbitMQ has published an overview of a new feature flag subsystem shipping in RabbitMQ 3.8. The purpose of this subsystem is to simplify rolling upgrades between releases that have incompatible or potentially incompatible changes.
RabbitMQ Docker image now ships RabbitMQ 3.7.14 and 3.7.15-beta.1 on latest Erlang and OpenSSL 1.1.1b
Java client 5.7.0 (for Java 8+) and 4.11.0 (for Java 6 & 7) have been released with usability improvements and dependency upgrades.
Reactor RabbitMQ 1.2.0 GA has been released, with a bug fix, dependency upgrades, and improvements in the publisher confirms support. Reactor RabbitMQ) is a reactive API for RabbitMQ based on Reactor and RabbitMQ Java client. Reactor RabbitMQ goal is to enable messages to be published to and consumed from RabbitMQ using functional APIs with non-blocking back-pressure and very low overhead.
Debian and RPM packages of several latest Erlang and Elixir releases are now available in Team RabbitMQ’s Erlang Bintray repository
Jason Farrell (@jfarrell) shared a demo of a .NET Core Hosted Service feeding stock price data into RabbitMQ and via PubSub communicating to a .NET Core Web app via @SignalR, all running in Kubernetes