Question: benefits of this extension and quarkus-smallrye-reactive-messaging-rabbitmq alternative about quarkus-rabbitmq-client

[bpasson]

As it is now, this extension will remain next to quarkus-smallrye-reactive-messaging-rabbitmq. There are upsides and downsides to using the reactive messaging extension. See issue #64 for more information on that part.

This extension is basically only exposing the RabbitMQ client as a managed bean for you to use as you see fit, where as the quarkus-smallrye-reactive-messaging-rabbitmq does a lot more, but also uses the Vert.x client in stead of the native RabbitMQ client.

This extension used to be listed in the Quarkus docs, but that broke down when Quarkus changed things with documentation. It hasn't been fixed yet on our side. We are working on it.

We still like to add dev mode support and code starts, but we are a small team as you might have seen. We will get around to adding those features and fixing the documentation.

It is up to you to decide which you want to use. If you have a need for access to the native RabbitMQ client this extension is the way to go I suppose. If the down sides to quarkus-smallrye-reactive-messaging-rabbitmq are no issue for you, you can go that way too. It integrates well with the rest of the reactive messaging stack.