To improve performance and reliability, vFabric RabbitMQ offers persistence, delivery acknowledgments, publisher confirms, high availability, and more. The following list highlights main features, including some enhancements that have been implemented since the release of vFabric RabbitMQ 2.4.1. For more details about vFabric RabbitMQ features, see the vFabric RabbitMQ Release Notes and Using vFabric RabbitMQ.
Flexible routing. Messages are routed through exchanges before arriving at queues. vFabric RabbitMQ features several built-in exchange types for typical routing logic. For more complex routing you can bind exchanges together or even write your own exchange type as a plugin.
Clustering. Several vFabric RabbitMQ servers on a local network can be clustered to form a single logical broker.
Federation. Federation offers an alternative distributed messaging model for servers that need to be more loosely and unreliably connected than clustering allows.
Highly available queues. Queues can be mirrored across several machines in a cluster, ensuring that even in the event of hardware failure your messages are safe.
Management UI. vFabric RabbitMQ ships with an easy-to use management user interface that allows you to monitor and control every aspect of your message broker.
Tracing. If your messaging system is not working properly, you can use the firehose feature to inspect every message that is published and every message that is delivered, per node and per vhost.
Wide-ranging operating system, client, and language support.. vFabric RabbitMQ implements support for all major operating systems and is compatible with clients written in many languages.
Plugin system. vFabric RabbitMQ ships with a variety of plugins, extending it in different ways, and you can also write your own.
Internal flow control. This feature can limit memory use and make performance more predictable if the server is overloaded.
Dead lettering ("Dead Letter Exchanges" subsection). When you declare a queue, dead lettering enables you to specify an exchange to which messages are redirected when they are rejected or expire.
Compatibility with Erlang R15B. Erlang R15B allows native operation on 64-bit Windows.