{product} acts as a proxy between your RabbitMQ application and {pulsar-reg} cluster. It implements the AMQP 0.9.1 protocol used by RabbitMQ clients and translates AMQP frames and concepts to {pulsar-short} ones. {product} can be run as a standalone Java application, a {pulsar-short} protocol handler, or a {pulsar-short} Proxy extension.
AMQP 0.9.1, the protocol RabbitMQ uses, employs the concepts of Exchanges, Queues, and Bindings to provide basic routing capabilities inside the message broker.
These concepts are mapped to {pulsar-short} topics and features.
{product} acts as a proxy and uses the {pulsar-short} binary protocol to communicate with the brokers. This method allows RabbitMQ applications to leverage {pulsar-short} features like load balancing of the topics on the brokers, batching of messages, partitioning of topics, and load balancing of the data on the consumers.
For more information, see operations:protocol-handler.adoc.
ROOT:partial$deployment-options.adoc
For instructions, see installation:getting-started.adoc.
|
Important
|
Support for topic exchanges was added in {product} version 2.10.1. |
{product} version 2.10.1 doesn’t support the following features:
-
Header exchanges
-
Exclusive consumers
-
Non durable exchanges and queues
-
Transient messages (all messages are persisted)
-
Authorization support
Because RabbitMQ and {pulsar-short} work differently, {product} was designed to realize the most benefit from {pulsar-short}'s scalability. This means that canceling an AMQP consumer re-queues the messages that were received through it because it also closes the associated {pulsar-short} consumers.