• Your options for supporting legacy RabbitMQ

    RabbitMQ 3.x support is ending – what are your options? TL;DR; Your options are:1. Upgrade now and stay on the supported path.2. Keep your legacy supported and make the upgrade manageable. How? Keep on reading!3. Risk losing support. What are your options for ongoing RabbitMQ support? Take a look at the options below that team…

    Read more

How to support legacy RabbitMQ
  • What Are Common RabbitMQ Configuration Mistakes and How Can You Avoid Them?

    What Are Common RabbitMQ Configuration Mistakes and How Can You Avoid Them?

    What Are Common RabbitMQ Configuration Mistakes and How Can You Avoid Them? RabbitMQ has sensible defaults for development and dangerous defaults for production. Most teams discover this the same way: a production incident that turns out to be a configuration value never changed from its starter setting. The mistakes are well known and the fixes…

  • What Are the Common Pitfalls to Avoid When Scaling RabbitMQ in a Production Environment?

    What Are the Common Pitfalls to Avoid When Scaling RabbitMQ in a Production Environment?

    What Are the Common Pitfalls to Avoid When Scaling RabbitMQ in a Production Environment? Scaling RabbitMQ is rarely a question of throwing more brokers at the problem. Most teams discover this only after a node has been added that did not improve throughput, or after a cluster has been expanded that did not improve availability.…

  • What Causes Excessive Management Database Memory Consumption in RabbitMQ?

    What Causes Excessive Management Database Memory Consumption in RabbitMQ?

    What Causes Excessive Management Database Memory Consumption in RabbitMQ? The RabbitMQ management plugin is the default way teams see what is happening inside the broker. It is also a significant memory consumer in clusters with many queues, exchanges, connections, or high churn. Most teams discover this only after the broker itself raises a memory alarm…

  • RabbitMQ vs MQTT (or, Why Are We Comparing a Messaging Protocol With a Message Queueing System?)

    RabbitMQ vs MQTT (or, Why Are We Comparing a Messaging Protocol With a Message Queueing System?)

    RabbitMQ vs MQTT (or, Why Are We Comparing a Messaging Protocol With a Message Queueing System?) If you dabble in message-based architectures, you must have heard of RabbitMQ and Message Queuing Telemetry Transport (MQTT). But just because they hang in the same places doesn’t mean they are the same. Now, you already know that, so…

  • Why Is the RabbitMQ Disk Space Alarm Triggered and How Do You Fix It?

    Why Is the RabbitMQ Disk Space Alarm Triggered and How Do You Fix It?

    Why Is the RabbitMQ Disk Space Alarm Triggered and How Do You Fix It? A RabbitMQ disk alarm is one of the most disruptive incidents a broker can produce. When the alarm is active, every publishing connection in the cluster is blocked, not just on the affected node. Production traffic stops upstream, queues stop growing…

  • RabbitMQ vs Redis: Choosing the Right Messaging System

    RabbitMQ vs Redis: Choosing the Right Messaging System

    RabbitMQ vs Redis: Choosing the Right Messaging System At first glance, comparing RabbitMQ and Redis Open Source Software (OSS) might seem like comparing apples and oranges. RabbitMQ is a dedicated message broker, whereas Redis OSS is an in-memory data store that also supports messaging.  However, because both can support asynchronous communication in microservice architectures, they…

  • What Common Mistakes Lead to RabbitMQ Message Loss and How Can You Prevent Them?

    What Common Mistakes Lead to RabbitMQ Message Loss and How Can You Prevent Them?

    What Common Mistakes Lead to RabbitMQ Message Loss and How Can You Prevent Them? RabbitMQ does not lose messages on its own. Message loss almost always happens at the seams: between a publisher that thinks it sent a message and a broker that never received it, or between a broker that thinks it delivered a…

  • What Are the Common Challenges Faced When Self-Supporting RabbitMQ?

    What Are the Common Challenges Faced When Self-Supporting RabbitMQ?

    What Are the Common Challenges Faced When Self-Supporting RabbitMQ? Self-supporting RabbitMQ is entirely viable. The broker is well-documented, the community is responsive, and most production deployments do not need exotic configuration. Teams hit trouble not because RabbitMQ is hard, but because the operational practice around it accumulates slowly while incident risk accumulates fast. Most self-support…

  • What Are the Top 10 RabbitMQ Troubleshooting Issues?

    What Are the Top 10 RabbitMQ Troubleshooting Issues?

    What Are the Top 10 RabbitMQ Troubleshooting Issues? RabbitMQ often becomes one of the first systems to show strain when distributed applications scale. Because it sits between services and carries work across the system, problems such as growing queue backlogs, memory alarms, disk alarms, connection churn, and stalled consumers can quickly escalate into service-wide incidents.…

  • RabbitMQ Commercial Support  Specialist support for running RabbitMQ effectively.

    RabbitMQ Commercial Support Specialist support for running RabbitMQ effectively.

    RabbitMQ Commercial Support Specialist support for running RabbitMQ effectively. RabbitMQ is generally very reliable, but when something does go wrong, it can have a serious knock-on effect. Unfortunately, in many cases, teams only realise how critical this message broker is only once something stops working. That’s why having access to experienced RabbitMQ specialists is so…