A companion to the Foojay podcast episode, this post distills the key questions and answers about Quarkus — from build-time optimization and live reload to JVM versus native trade-offs and cloud cost savings.

Understanding the rationale behind dropping official support for GraalVM/Mandrel 23.1 for JDK 21 on native image builds.

Quarkus 3.35 introduces Profile-Guided Optimization (PGO) support for native images. Enable it with quarkus.native.pgo.enabled=true and let your integration tests drive the profiling - the build automatically produces an optimized native binary tailored to your application's actual runtime behavior.

Quarkus continues to focus on native for swift start-up time and low memory footprint.

Mandrel 25, based on GraalVM 25, has been released.

We bring you some tips on how to develop Quarkus applications deployed to a Raspberry Pi.

Generating and inspecting heap dumps in Quarkus native when `OutOfMemoryError` errors occur

Learn how to containerized applications using virtual threads.

A comprehensive analysis attributing binary size increase to specific changes in Mandrel's code base.

A comprehensive analysis attributing binary size increase to specific changes in Mandrel's code base.

Learn how to compile applications using virtual threads into native executable.

Use Linux native tooling and JFR to understand Quarkus Native startup RSS consumption

Learn more about how you can profile and monitor Quarkus native executables with JFR.

Native runtime GC policy switches to adaptive to more consistency and predictability

NativeJDB bridges the gap between the Java Debugger (JDB) framework available in modern IDEs and native debugging via GNU Project debugger (GDB).

How does Quarkus make your native executable smaller using UPX

Inspect the call paths that get included into a Quarkus Native app with Neo4j

Running a Quarkus native app inside a container on a Raspberry Pi