Reactive Routes vs RestEasy Reactive

[justinjohnson02]

Question - is there a difference in the future roadmap/direction for Quarkus between Reactive Routes and RestEasy Reactive?

While I have experience with Vert.x, I don't have as much with Mutiny/RestEasy Reactive and enjoy the flexibility that comes with RoutingContext - though I am more than open to seeing how to "migrate" to Mutiny.

In the end though, I just wanted to try and "align" our code somewhat with the direction of Quarkus when it comes to REST extension development.

Thanks and awesome work to the entire team + contributors

[quarkus-bot[bot]]

/cc @FroMage, @geoand, @stuartwdouglas

[ghubstan]

Can I leave my repo classes alone, keep them returning io.vertx.core.Futures, and use the bindings in the calling (web-service) layer of the app? I see my Quarkus app already imports smallrye-mutiny-vertx-core, and related binding modules.

I just don't see how I can transform a io.vertx.core.Futures completion result into a 'Uni<?>', using the bindings?

[geoand]

Can I leave my repo classes alone, keep them returning io.vertx.core.Futures, and use the bindings in the calling (web-service) layer of the app

I don't see why not.

I just don't see how I can transform a io.vertx.core.Futures completion result into a 'Uni<?>', using the bindings?

There is io.smallrye.mutiny.vertx.UniHelper#toUni

[ghubstan]

Thanks. I just found the helpers in smallrye-mutiny-vertx-runtime. Once again, I embarrassed myself by posting a question, then finding out myself a minute later ;-/

[ghubstan]

Perfect, in the web gateway service layer, I can make calls to my vertx-only db repos:

io.vertx.core.Future<VendorRecord> vertxFuture = vendorRepository.fetchVendorWithId(id);
Uni<VendorRecord> uni = UniHelper.toUni(vertxFuture);

I need to understand the 'async' implications of Uni.createFrom().completionStage(future.toCompletionStage()), but I know where to get the answers now. Thanks for your patience.

[geoand]

🙏🏼