Starlight for RabbitMQ proxy extension

Following the proxy extension interface, Starlight for RabbitMQ constructs a gateway service that monitors RabbitMQ channel(s).

Both the proxy extension and the protocol handler use the same gateway logic for functions like creating channels, managing exchanges, and publishing messages. To learn more about these functions, see Starlight for RabbitMQ protocol handler.

One notable difference between the Starlight for RabbitMQ proxy extension and the protocol handler is that the proxy runs on the Pulsar Proxy. This means that a discovery must be done at startup to find available brokers. The Starlight for RabbitMQ proxy extension uses the broker discovery mechanism provided in the Pulsar proxy extension interface to discover brokers. It then chooses the first available broker from that collection. All messages to the Starlight for RabbitMQ service are produced using that broker.

Was this helpful?

Give Feedback

How can we improve the documentation?

© Copyright IBM Corporation 2026 | Privacy policy | Terms of use Manage Privacy Choices

Apache, Apache Cassandra, Cassandra, Apache Tomcat, Tomcat, Apache Lucene, Apache Solr, Apache Hadoop, Hadoop, Apache Pulsar, Pulsar, Apache Spark, Spark, Apache TinkerPop, TinkerPop, Apache Kafka and Kafka are either registered trademarks or trademarks of the Apache Software Foundation or its subsidiaries in Canada, the United States and/or other countries. Kubernetes is the registered trademark of the Linux Foundation.

General Inquiries: Contact IBM