Get started with VMware Tanzu RabbitMQ
Thank you for your interest!
We will get back to you shortly.
Deployments running in different zones or regions can keep their schemas in sync thanks to VMware's exclusive Warm Standby Replication feature. If the primary deployment becomes unavailable, clients are able to reconnect to the secondary and continue working with minimal disruption.
All network traffic exchanged by nodes in a deployment is compressed by default. For JSON message payloads, bandwidth usage is reduced by 16x. Use the calculator below to see how much you can save in network bandwidth costs.
Transport security protocols are restricted to production-safe variants. The included Erlang runtime has the latest optimizations and patches applied. Recovery from crashes is quicker and disk usage is lighter via improved configuration.
The following table provides all you need to know about the Open Source RabbitMQ product and the VMware Tanzu RabbitMQ enterprise products. This table lists the key features that come with each product, a brief description about how to run them, and key product page and documentation links.
| Open Source RabbitMQ |
VMware Tanzu RabbitMQ for Tanzu Application Service | VMware Tanzu RabbitMQ OVA | VMware Tanzu RabbitMQ OCI | VMware Tanzu RabbitMQ for Kubernetes | |
| Type | Open source | Enterprise | Enterprise | Enterprise | Enterprise |
| Description | Open source RabbitMQ. Mature, reliable, and general purpose. | RabbitMQ for Tanzu Application Service | RabbitMQ for VMs | RabbitMQ for VMs using container runtime | RabbitMQ for Kubernetes. Easy deployment and automations. |
| Key features | Support (when licensed) |
Support Erlang Open SSL |
Support Erlang Open SSL Intra-cluster Compression Warm Standby Replication |
Support Erlang Open SSL Intra-cluster Compression Warm Standby Replication |
Support Erlang Open SSL Intra-cluster Compression Control Plane Warm Standby Replication Cluster Operator Topology Operator |
| Key links | OSS RabbitMQ site | Docs Product page Tanzu Application Service |
Docs Product page |
Docs Product page |
Docs Product page |
VMware Tanzu RabbitMQ reduces your public cloud bandwidth bill using its exclusive intra-cluster compression feature.
The enterprise version of RabbitMQ pays for itself by reducing your cloud bill.
Approximate monthly, per-deployment savings based on the following calculations:
When a multi-node RabbitMQ cluster runs across multiple availability zones, all data transferred between nodes is charged at $0.01/GB. Google Cloud charges for outgoing traffic only. Amazon Web Services and Microsoft Azure charge for both incoming and outgoing traffic.
This is based on 1 Quorum Queue with 5 Producers and 5 Consumers, each with its own dedicated Connection and Channel. We use the c2-standard-8 GCP instance type, with 4 vCPUs and 10GB RAM dedicated to each RabbitMQ node. Each node has a 500GB SSD disk with max 15k read and write IOPS, and 240MB/s read and write throughput. Disk write throughput is the limiting factor, and the sliders on the left readjust to reflect this.
Yes, and that support also includes a license to VMware Tanzu RabbitMQ, which we strongly recommend. However, it’s up to you to use the open source or the enterprise distribution.
No, your VMware Tanzu RabbitMQ license includes support for both the VMware Tanzu RabbitMQ and the RabbitMQ distributions for the number of cores in your license.
In the past, RabbitMQ used only queues and Kafka streams. RabbitMQ has increased its functionality and now has both queue semantics and streams, whereas Kafka still only supports streams. Read more about RabbitMQ vs. Kafka.
Yes, streams is a feature of both the open source RabbitMQ and the enterprise VMware Tanzu RabbitMQ distributions. Watch a webinar on RabbitMQ Streams.
We will get back to you shortly.