Quarkus 1.5.0.Final welcomes new extensions
Keep up with Quarkus; let’s take a closer look and see what’s new with the supersonic subatomic Java. The latest update, version 1.5.0.Final adds new extensions, bug fixes, and a few performance upgrades. Let’s take a look at everything under the hood.
Another release from Quarkus is here and ready to download. Quarkus 1.5.0.Final was announced on June 3, 2020. It includes a number of new updates, new extensions, as well as the usual bug fixes and a few performance improvements.
What is Quarkus? Sponsored by Red Hat, it is a “Kubernetes Native Java stack tailored for OpenJDK HotSpot and GraalVM, crafted from the best of breed Java libraries and standards”.
Keep up with Quarkus; let’s take a closer look and see what’s new with the supersonic subatomic Java.
Included in the new release:
- Support for Picocli: Create rich command line apps that run off of the JVM with the Picocli extension. This feature is currently experimental.
- gRPC support: Write clients and services with gRPC. You can configure with either Maven or Gradle.
- MicroProfile GraphQL extension
- Amazon service support: Added for Amazon DynamoDB, Amazon KMS, Amazon S3, Amazon SES, Amazon SNS, and Amazon SQS.
- Hibernate ORM REST Data with Panache extension: Refer to the guide and learn how this experimental feature simplifies CRUD REST APIs based on JAX-RS and Hibernate ORM.
- Support for Spring Cache annotation and new documentation
- Blaze Persistence extension
- Support for @InjectSpy
- New documentation updates: Amazon Lambda, fixed Quartz documentation formatting, Add Credentials Provider, and added docs for all new extensions.
- Fixes: Fixes for several Mongo test failures, issues with running tests in the IDE, improved error handling during Amazon Lambda Test Framework shutdown.
View the full changelog for 1.5.0.Final on GitHub.
Fast-jar packaging format
One of the major highlights in this release is the newly added fast-jar packaging format.
According to the announcement blog, this new format will make startup times even faster and is a new alternative to the default jar packaging format.
Quarkus users should note that this format may become standard in future additions. Familiarizing yourself with the new format and providing the dev team with feedback before then is recommended.
Making the switch
Have you tried using Quarkus? It is finding its foothold in the enterprise.Recently, the consulting company Sedona rewrote its insurance premium actuarial engine using Quarkus.
Read about their journey here and see what benefits the switch provided. According to the blog, the five top reasons to switch were:
- Quarkus has a container-first approach
- It is Kubernetes-native
- It has a fast start-up time
- It consumes little RAM
- Live coding
Join the mailing list to stay updated with new releases, feature development, plans for the future, and join the developer community.