Quarkus is a Java framework for building cloud-native apps. It is fully supported by devonfw as an option and alternative to spring. Additional things like extensions will be available on the devon4quarkus GitHub repository.
Quarkus offers the following benefits:
-
fast turn-around cycles for developers
Save changes in your Java code and immediately test the results without restarting or waiting -
faster start-up and less memory footprint
When building your app as native-image via GraalVM it gets highly optimized. As a result it starts up lightning fast and consumes much less memory. This is a great advantage for cloud deployment as well as for sustainability. -
clean and lean As quarkus was born as cloud-native framework it is very light-weigth and does not carry much history and legacy.
Quarkus has the following drawbacks:
-
less flexible
Quarkus is less flexible compared to spring or in other words it is more biased and coupled to specific implementations. However, the implementations just work and you have less things to choose and worry about. However, in case you want to integrate a specific or custom library you may hit limitations or lose support for native-images especially when that library is based on reflection. Therefore, check your requirements and technology stack early on when making your choice. -
less established
Since quarkus was born in 2019 it is modern but also less established. It will be easier to get developers for spring but we already consider quarkus mature and established enought for building production ready apps.