How deeply does Quarkus in Action cover native executable?

Explains ahead-of-time compilation and platform specificity, then gives build and run commands without detailing GraalVM internals.

Native executable

As explained in Quarkus in Action

A native executable is a standalone machine-code program that runs directly on a target operating system and processor architecture without requiring a managed runtime.

A native executable is a platform-specific machine-code build of a Quarkus application. GraalVM native-image compiles Java code ahead of time and includes the application code, required library code, language runtime, and linked JDK code. Closed-world analysis determines what the executable needs at run time. Unlike a runnable JAR, it runs without starting a JVM; a binary built for Linux will not run on Windows. section 2.4.1 section 2.4.2

To build and run one from a generated Quarkus project:

Use `./mvnw package -Pnative`, `./gradlew build -Dquarkus.package.type=native`, or `quarkus build --native`. section 2.4.4
Run the generated binary directly, for example `./target/quarkus-in-action-1.0.0-SNAPSHOT-runner`. Its filename may differ by platform. section 2.4.4
Allow more build time and memory than for ordinary packaging; native compilation can take several minutes. section 2.4.4

If GraalVM or Mandrel is unavailable locally, Quarkus can build inside Docker or Podman. Request this with `-Dquarkus.native.container-build=true`; Quarkus may also fall back to a container build when it cannot find `native-image`. This route produces a Linux executable, suitable for a Linux-based container image even when the host uses another operating system. section 2.4.5

Choose the format for the workload, not as an automatic final step. Fast startup makes native executables attractive for serverless deployments. A long-running JVM application can eventually achieve higher throughput through just-in-time optimization, while native compilation fixes its optimizations ahead of execution. section 2.5.1 section 1.2.2

How Quarkus in Action covers it

liveBook manning.com

Read Quarkus in Action on liveBook Get the book at manning.com

Also explained in

liveBook manning.com

Logs and TelemetryA native executable is a compiled program produced for a specific operating-system and hardware platform and run directly by that platform.
liveBook manning.com

The Art of CodeNative execution runs compiled program code directly for a target operating-system and processor platform without an intermediate virtual-machine execution layer.
liveBook manning.com

Learn Docker in a Month of Lunches, Second EditionA native binary is an executable program compiled for a specific operating-system and processor platform without requiring a separate language runtime.

Compare how 4 books explain native executable →

Related concepts

Goproduced by · Go is a statically typed, compiled, garbage-collected programming language with built-in support for concurrency.
ahead-of-time compilationproduced by · Ahead-of-time compilation is the translation of program code into executable or loadable form before program execution begins.
GraalVMproduced by · GraalVM is a polyglot runtime and development platform for running and compiling applications in Java and other programming languages.
native compilationproduced by · Native compilation is ahead-of-time compilation of application code into platform-specific machine code that runs without a just-in-time compiler.
native imageproduced by · A native image is a standalone executable produced by compiling an application and its required runtime components ahead of execution.
configuration profileconfigured by · A configuration profile is a named collection of settings that selects a particular software operating, installation, connection, or service configuration.

This explainer was generated by Manning's knowledge graph from the text of Quarkus in Action. The section links point to the parts of the book it draws on.