Quarkus 3.0, our new major release, is here!

Quarkus 2 introduced the Dev UI, which provides a web UI to use during development. Extensions could provide their own Dev UI pages to provide additional functionality.

Quarkus 3.0 now has a new Dev UI that is more extensible and easier to use. It also has a new and much-improved look and feel.

The new Dev UI is available by default. However, because not all the extensions have migrated to the new Dev UI, you can still access the old one at /q/dev-v1. The old Dev UI is planned for removal in a future version.

We have a playlist on Quarkus YouTube channel that shows off the new Dev UI, explains the new features and how to use and extend it.

Quarkus 2 was based on Jakarta EE 8. Quarkus 3 is based on Jakarta EE 10.

The most visible change is that the javax.* packages from Jakarta EE have been moved to jakarta.*. This change requires changing any source code and dependency and its transitive dependencies that rely on the javax.* packages.

See the Updating to Quarkus 3.0 section for more information on how quarkus update helps you migrate.

The change to target Jakarta EE 10 brings two major improvements:

Eclipse MicroProfile 6.0 aligns with Jakarta EE 10 Core Profile and replaces MicroProfile OpenTracing with MicroProfile Telemetry.

One of the biggest changes in Quarkus 3 is that we upgraded Hibernate ORM from version 5 to version 6.2.

Hibernate ORM 6 is a new major release, and it comes with many changes, some of them breaking.

To learn more about the changes in Hibernate ORM 6 from a Quarkus user perspective, see Hibernate ORM 5 to 6 migration.

The Hibernate ORM release announcements have a lot of information about the changes/improvements in Hibernate ORM 6:

Upgrading to Hibernate ORM 6 will require some effort and testing. Make sure you have a look at the Updating to Quarkus 3.0 section below.

Some improvements have also been made to the Quarkus Hibernate ORM extension itself, such as:

Hibernate Reactive has been upgraded to version 2.0 to be compatible with Hibernate ORM 6.

Quarkus was upgraded to Mutiny 2 and now uses the Java Flow API instead of Reactive Streams.

Developer experience is a key aspect of Quarkus, and we are constantly improving it.

Until now, all the Quarkus endpoints were exposed on the same network interface.

Starting with Quarkus 3.0, you can expose technical endpoints such as the health and metrics on a different interface thanks to a specific management interface.

To expose information about your application (such as the git hash), add the quarkus-info extension to your project.

The endpoint is available on /q/info and will be exposed on the management network interface if you enable it.

Many usability enhancements have come into RESTEasy Reactive, such as retrieving all multipart parts.

Remember that RESTEasy Reactive is our default REST layer covering both reactive and blocking workloads.

The OpenTelemetry extension has been rewritten to support the SDK autoconfiguration and went through many changes.

The configuration namespace has changed to quarkus.otel.*. We recommend switching to the new configuration properties, even though the old ones are still supported for now.

Also, enabling OpenTelemetry for JDBC is now as simple as setting quarkus.datasource.jdbc.telemetry to true. You don’t have to modify your JDBC connection URL anymore.

Sending emails via multiple SMTP servers is supported in Quarkus 3.0.

Have a look at the updated documentation.

Qute, our templating engine, also got a lot of love with several new features, such as the ability to cache a section of the template that rarely changes thanks to cached sections.

It is now possible to use a Redis backend with the Cache extension.

For more information, see the dedicated guide.

The cache extension also allows you to define a global default cache configuration that will be applied to all your caches.

Your database migrations with Flyway and Liquibase are now run as init containers in manifests.

The notion of migration/setup work being done in init containers is available for other extensions to implement and support.

The Flyway extension supports custom credentials/URLs to connect to the database and you can more easily customize the configuration of the Flyway instance.

CredentialsProviders are now supported for MongoDB connections.

The new Elasticsearch Java Client is supported as a brand-new extension. This solves the licensing problems that prevented us from updating the deprecated High Level REST Client.

To use this new client, have a look at the updated Elasticsearch guide.

Several enhancements have been made to the gRPC extensions, such as the support of InProcess.

You can now schedule jobs programmatically by using the Scheduler programmatic API, described in the Scheduler reference guide.

The Kubernetes Client has been upgraded to version 6.5.

The development of Azure functions is easier than ever, thanks to the new Azure Functions extension.

Learn more about it in the dedicated guide

We have been working hard to make sure that the Quarkus Platform is ready for production use. Not every extension found in Quarkus 2 Platform is available or not yet final in Quarkus 3 Platform yet, but they are on their way.

The following extensions are available:

The following extensions are not yet available, but will be available soon:

If you are using an extension that is missing or not working, please open issues in their respective issue tracker systems.

The OpenJDK community will end active support for Java 11 in September 2023. We still plan to support Java 11 past that date for core Quarkus functionality, but Java 11 is now marked as deprecated. We recommend that you upgrade to Java 17 or later if you want to use the latest and greatest version of Quarkus.

With Quarkus 3 finally out, we will be returning to our regular, continuous cadence of releasing approximately every five weeks. This provides a delivery train of small incremental changes that are easy to adopt and upgrade to.

We do know some of you are looking for a more stable release cadence, and we are working on a new long-term support (LTS) policy starting from Quarkus 3.2. We will provide details on this as we get closer to the 3.2 release. Java 11 will still be supported there for the core part of Quarkus.

Quarkus is not just the https://github.com/quarkusio/quarkus repository and the Quarkus platform. It is also the whole rest of the Quarkus ecosystem - the so-called Quarkiverse. Those extensions are hosted and maintained by lots of contributors and organizations around the world. Some host these extensions in their GitHub repositories, and others host them in the Quarkiverse Hub.

With Quarkus 3, due mainly to the package changes in many of the core dependencies, we are happy to say that lots of those extensions have already been updated to work with Quarkus 3.0. We are working with the maintainers of the remaining extensions to get them updated as well.