Quarkus Java framework adds dev extensions for observability

By Paul Krill

Quarkus 3.11, the latest version of the Red Hat-sponsored Kubernetes-native Java framework, has been released. The update introduces dev extensions for observability and an experimental WebSockets extension.

Quarkus 3.11 was announced May 29. Developers can update by using the latest version of the Quarkus CLI and running quarkus update.

Discussing the dev extensions for observability in a blog post, Red Hat software engineer Guillaume Smet noted efforts have been made to simplify the setup of development resources for observability, including resources for Grafana, Jaeger, OTel, and VictoriaMetrics. These can be used in contexts including reusable dev services, simple start/stop dev services, and the single/plain per QuarkusTestResource dev service.

Dev extensions in Quarkus are used to automate the provisioning of unconfigured services in development and test mode. With observability dev services, the intent is to provide a way to orchestrate and connect more than a single dev service. Also, beginning in Quarkus 3.11, /mvnw quarkus:run can be used to start dev services, so a favorite service can be started automatically as a container.

Quarkus 3.11 introduces the Websockets.next extension, both client and server, in an experimental phase. With Quarkus 3.11, builders added the ability to easily define WebSockets and an initial version of security integration. More features will be added in upcoming releases.

Also in Quarkus 3.11, a new Infinispan Cache extension supports the use of Infinispan as a back end. And on the security front, Quarkus 3.11 includes support for an OIDC (OpenID Connect) session expired page and introduces OidcRedirectFilter, which allows for the customization of OIDC redirects.

© Info World