days
0
-41
-5
hours
-1
-4
minutes
-1
-1
seconds
-5
-7
search
New extensions, HTTP/2 support, & more

Quarkus 1.4.1.Final deprecates Java 8

Sarah Schlothauer
quarkus
© Shutterstock / Sunward Art

Quarkus 1.4.1.Final arrived with several new features. This version deprecates Java 8; users are now recommended to use Java 11. It also introduced a new FaaS framework and a new command mode for building command line apps.

The latest monthly Quarkus release is out, as announced by Guillaume Smet. Version 1.4.1 Final includes several new features (and of course, many bug fixes).

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”.

Check out their benchmark reports to read about its performance in imperative and reactive workloads. Let’s have a look at what’s new in this open source framework.

SEE ALSO: The new JavaScript Magazine – now available as free download

Quarkus 1.4.1.Final

Here are some of the highlights:

  • Java 8 deprecated. Users are recommended that they use Java 11 from now on. According to the announcement blog, Java 8 support is planned to be dropped in “roughly two months’.
  • Support for HTTP/2: Enabled by default.
  • Funqy framework: Funqy is a FaaS framework that improves functions for Amazon Lambda, Amazon Lambda with RESTEasy, Undertow, or Vert.x Web, and Azure Functions with RESTEasy, Undertow, or Vert.x Web.
  • Integration with Mockito: Improves mocking CDI beans.
  • New default Vault version: Vault KV Secret Engine defaults to version 2 and adds support for the Vault TOTP engine.
  • Keycloak Admin Client extension added
  • Native support for Amazon Alexa
  • LDAP authentication support
  • Updated SmallRye Reactive Messaging to 2.0

View the full changelog on GitHub.

New command mode

One of the biggest features is the new command mode for building command line apps with Quarkus.

The updated documentation examines this new feature, its lifecycle, and Dev mode.

From the docs, the basic command mode application lifecycle is:

  1. Start Quarkus
  2. Run the QuarkusApplication main method
  3. Shut down Quarkus and exit the JVM after the main method returns

SEE ALSO: Duolingo migrates from Java to Kotlin, reducing line count 30%

Updating to the latest version

Before you update, refer to the migration guide and take note of the following changes and updates, as they may potentially require some code tweaks:

  • MongoDB updated to client version 4
  • JVM Arguments parameter changed to a List
  • Deprecated the ./gradlew buildNative task
  • Kogito moved out of the Core repository into the Quarkus Platform
  • Hibernate Search 6.0.0.Beta6 changes and feature preview
  • OidcTenantConfig package moved to io.quarkus.oidc package

Newcomers should view the getting started guide before their supersonic subatomic Java journey.

In addition to the new features, Quarkus also added a new public document listing organizations that use Quarkus. Organizations such as Lufthansa Technik and Vodafone Greece have shared their experiences and benefits of using Quarus.

If you have a story to share with them, please do!

Author
Sarah Schlothauer

Sarah Schlothauer

All Posts by Sarah Schlothauer

Sarah Schlothauer is an assistant editor for JAXenter.com. She received her Bachelor's degree from Monmouth University and is currently enrolled at Goethe University in Frankfurt, Germany where she is working on her Masters. She lives in Frankfurt with her husband and cat. She is also the editor for Conditio Humana, an online magazine about ethics, AI, and technology.

guest
0 Comments
Inline Feedbacks
View all comments