Consider Quarkus #2
Description
It appears all new Java web apps will likely use Quarkus going forward. However, existing smoothness apps might just stick with Wildfly. Something to think about.
Quarkus is likely to get most of the optimizations and attention going forward, and it appears to be much easier to customize what libraries and frameworks are provided. It's reportedly faster, smaller, and easier to use as well.
The situation for customizing Wildfly is painful - you either:
- Accept the pre-built distribution with whatever it comes with
- Use the not-so-easy to customize galleon tool to try to customize, or else
- Use the no longer maintained gradle-plugin for provisioning
- Use the not-so-easy to customize jboss modules directly (via jboss-cli)
- Package everything into your war file (possibly making it huge and duplicating different versions of provided libs)
- Some combination of the above (at the moment we're using the "easy, but bloated unzip install", plus leveraging the older, but provided Hibernate, providing a flag to optionally package some dependencies with the war file, and providing some scripts to install dependencies into Wildfly via jboss CLI.
For example, smoothness uses the keycloak admin client library, which is a pain to install into Wildfly. With Quarkus there is a pre-built package
However, Quarkus doesn't support EJB and a few other features supported by Wildfly. Some refactoring would be needed (possibly replace EJB with CDI).