Jignesh Patel wrote:yup, I don't want to deploy quarkus on wildfly, I would rather deploy on kubernetes container on aws, but I need to define a bridge between application deployed in wildfly and kafka application deployment in quarkus.
Ok so you need to re-think a little how Quarkus is different to Wildfly. Let's compare these two for what it's worth.
Wildfly is a general purpose
JEE application server. Supporting standardised JEE apis. Two profiles are supported Full profile and Web profile. Apps packaged in all sorts (Jar, War, Rar, blah) of formats can be deployed. The deployment of many Enterprise apps in the server is possible.
Whereas Quarkus is akin to a framework. Like Dropwizard but very different end goals in mind. It's a re-evaluation from the ground up what's really necessary to provide very light weight (small footprint) applications in a container platform. Aka "Microservices". Plus it has build time
Maven plugins (dark magic) that analyse your Microservice code and strips out absolutely everything which isn't going to be necessary at runtime. With the build time option to generate a native binary for very efficient memory consumption at the expense of other things. Deployment here will be a distinct container (or pod) on AWS. The native binary option makes Java a viable platform that does achieve equivalent service deployment density to other languages.
I hope you can now see Wildfly and Quarkus are not exactly achieving the same level of sophistication or capabilities.
This isn't to say you cannot deploy your current application with Wildfly. It is certainly possible. You can run more sophisticated applications but the service deployment density will be lower.
To answer your question.
To adapt/bridge an application to run as a containerised Quarkus service will probably involve a re-write. With Quarkus there is a suite of carefully selected APIs that will
most likely be used in Microservice type (shape) applications. You are best spending 10 minutes noting down the feature spec apis in your application. Then ticking off each you can find available on the Quarkus
https://code.quarkus.io/ website. You might find your current application is not the same "shape" as a Microservice.
Also have a look at the Microprofile forum [1] to see what's made available from the "standardised specification" community for developers. You might find an option there that lowers the necessary transition investment.
[1]
https://coderanch.com/f/211/microprofile
