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 to create channels, manage exchanges, publish messages, etc. To learn more about all those functions refer to the "Starlight for RabbitMQ protocol handler" document.

One notable difference between the Starlight for RabbitMQ proxy extension and the protocol handler, is that the proxy runs on the Pulsar Proxy. So a discovery must be done at startup to find available brokers. Currently, 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 will be produced using that broker.

Was this helpful?

Give Feedback

How can we improve the documentation?

© 2024 DataStax | Privacy policy | Terms of use

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: +1 (650) 389-6000,