Quarkus 1.0 and SpringBoot

An airhacks.fm conversation with Dimitris Andreadis (@dandreadis)
about: eclipsecon, Quarkus 1.0 and 1.0.1 releases, Quarkus is 8
months young, more extensions, more reactive functionality, 97
external committers and 93 RedHat committers, opinionated view vs.
expansion and experimentation, Quarkus long term support, the three
levels of extensions, quarkus extensions registry, the idea of
composite extensions, emulating the composite extensions with a
no-op extension, emulating the "all" injection setting in
beans.xml, Quarkus uses Jandex for annotation searching, there is
no greenfield development, many new developers are coming from
SpringBoot, Kubernetes Native Spring apps on Quarkus by Georgios
Andrianakis, Vodafone Greece replaces SpringBoot with Quarkus, the
business case of SpringBoot to Quarkus migration was RAM
consumption, boot time improvement with Quarkus, J9 JVM improves
startup time, external dependencies are bad for startup time,
Quarkus power is Java optimization, Quarkus optimises the standard
Java HotSpot application, GraalVM optimizes it even further,
Quarkus performs Hibernate optimizations at build time and not
deployment time, Quarkus does not include SpringBoot library,
Quarkus provides a Spring API compatibility layer which is
converted at build time, Spring is emulated on Quarkus, the Spring
compatibility layer was implemented in a month, Quarkus is built on
20 years old wisdom like Hibernate or Transaction Manager etc, in
the Vodafone case, Quarkus reduced 60% of RAM, with memory savings
come cost savings, the fast boot time is important for scaling in
the clouds, Quarkus is comparable to React -- comes with free
memory improvements without migrations, Quarkus ships with Vert.x,
the Quarkus Vault extension, the SpringBoot compatibility layer is
conceptually similar to Linux Wine compatibility layer, Quarkus
would like to stay away from EJB, EJBs are faster than CDI on
regular application servers on Quarkus the performance could be
comparable with RequestScoped, Quarkus ships with built-in CORS
filter, Keycloak supports oauth flows with a Gateway (Gatekeeper),
Quarkus comes with native JWT Microprofile support, two Quarkus
books are in the pipeline, keeping the conventions and usability of
Quarkus could become a challenge, Quarkus will also come with tight
OpenShift integration, the Engineering Director of the Extended
Quarkus Team

Dimitris Andreadis on twitter: @dandreadis and
dandreadis.blogspot.com