Most common Quarkus extensions
Quarkus is aiming at cloud-native applications and microservices but shares some features and functionalities with the JEE world. This is thanks to its adherence to the MicroProfile specification.
Such features are implementing common use cases and are very handy, as they allow you to use existing skills and, in some cases, existing JEE code.
In this section, we will go through a quick overview of the Quarkus extensions shared with the JEE specification.
Content Dependency Injection
CDI is a structured way to wire and compose the objects of your application. CDI in Quarkus is based on the Contexts and Dependency Injection for Java 2.0 specification, which defines CDI for both Java SE and Java EE.
The Quarkus CDI implementation leverages the ArC framework and is not fully compliant with the CDI specification, even if it provides support for the most common CDI use cases such as DI (of course), qualifiers, life cycle callbacks, and interceptors...
