Quarkus, the Java framework for microservices initially released by RedHat in March 2019, has reached version 2.7.1. But before looking at what's new, let's take a look at what Quarkus does differently and how it contributes to the current popularity of Java.
Describing Quakus as a "Java framework for microservices" isn't 100% accurate. Despite the fact that Quarkus was created with microservices in mind, you can also build monoliths with it. Also, while Java is the primary language, you can write Quarkus programs in Kotlin and Scala as well.
Quarkus, together with Micronaut and Helidon, is part of a new league of open-source frameworks that have sprung up in the last few years in order to boost the usage of Java in the microservices world. Java supremacy in this arena was under threat due to the bloat that existing frameworks were burdened with - hundreds of class files required, resolving dependencies at runtime, use of reflection, large memory footprint, extended warm up time. Spring and Jakarta EE were the typical perpetrators.
Spring of course is a monumental piece of technology - a versatile framework that does a lot under the covers to boost developer productivity. That magic comes with a drawback, however. The magic Spring pulls is happening at runtime, analyzing your code and the annotations, injecting beans, etc thus using a lot of runtime loading as well as reflection under the hood.
full article on i-programmer:
https://www.i-programmer.info/news/80-java/15223-quarkus-271-released.html
Comments