Introducing Mutiny

[cescoffier]

Description

The objective of this epic is to gather all the tasks related to the introduction of Mutiny in Quarkus, as well as the deprecation of Axle and RX APIs, documentation and quickstart updates...

Tasks

• Create the Mutiny extension - Add support for Vert.x Mutiny #7098
• Integrate Mutiny in the Vert.x extension, and manage Axle / RX deprecation - Add support for Vert.x Mutiny #7098
• Integrate Mutiny with @ConsumeEvent - Add support for Vert.x Mutiny #7098
• Integrate Mutiny with RestEasy - Implement Resteasy Mutiny support #7177
• Integrate Mutiny with Context propagation - Implement Context Propagation support for Mutiny #7303
• Update Vert.x quickstart to use Mutiny instead of Axle - Update various guides to Mutiny #7388
• Integrate Mutiny in Qute - Integration of Qute and Mutiny #7101
• Update the mailer extension as well as the guide - Implement Mutiny support for the mailer service #7211
• Integrate the Mutiny API with the PostGreSQL and MySQL reactive client - this includes updating the guide - Update the reactive database client extensions to use Mutiny #7216
• Integrate Mutiny API in the reactive Mongo API - Implement the Mutiny API for the MongoDB client #7263
• Write a Mutiny quickstart
• Integrate Mutiny Verticle - Add support for MutinyVerticle #7231
• Add Uni and Multi support to Reactive Messaging - partially done
• Switch Mail Qute template support to Mutiny
• Update Panache Mongo (reactive version) to provide a Mutiny API Mongodb panache/mutiny #7327
• Use Mutiny API in Quarkus Security

[loicmathieu]

@cescoffier it's still time for MongoDB with Panache to replace the Axle base implementation to a Mutiny one, I can do it easily.

Provinding both implementation is more works (the deployment part of MongoDB with Panache is complexe).

I can work on it this week based on your mongodb-client branch, my only question is do we expose Uni/Multi or do we stick with CompletionStage/Publisher ?

[cescoffier]

@loicmathieu ideally both. In your Panache code, the Axle model is in the axle package. Just create the mutiny one in the reactive package.

So:

1. Deprecate io.quarkus.mongodb.panache.axle.ReactivePanacheMongoEntity
2. Create io.quarkus.mongodb.panache.reactive.ReactivePanacheMongoEntity

[loicmathieu]

@cescoffier the Axle implementation was merged a few days ago so nobody already used it. So we can still replace it. Having a new thing already deprecated seems strange ...

[emmanuelbernard]

@cescoffier I'll move this out of the roadmap board as the remaining tasks are more focused now. We could create a more specific subsequent epic if you feel it needs visibility at the roadmap level

[cescoffier]

All Done!