Quarkus aims to make Java a leading platform in Kubernetes and serverless environments while offering developers a unified reactive and imperative programming model to address a wider range of distributed application architectures optimally.

Mandrel is a downstream distribution of GraalVM CE, supporting the same capabilities to build native executables but based on the open source OpenJDK.

[7] From the beginning, Quarkus was designed around the container-first and Kubernetes-native philosophy, optimizing for low memory usage and fast startup times.

These design principles reduce the size, and ultimately the memory footprint, of the application running on the JVM while also enabling Quarkus to be natively-native.

When running in development mode the workflow is simply: Write Code → Refresh Browser → Repeat This will work out of the box, with no special setup required.

For example, a developer can do test applications if they work in the production database, PostgreSQL rather than H2 in-memory datastore in the application.properties file: quarkus.datasource.devservices.image-name=postgres:latest DevServices is generally enabled by default unless there is an existing configuration present.

When DevServices is enabled Quarkus will attempt to automatically configure and start a database when running in development or test mode.

Developers probably think of external continuous integration (CI) tools that a QA team most likely has responsibility for verifying test cases.

Developers do not have to spend lots of time learning an entirely new set of APIs and technologies to take advantage of the benefits Quarkus brings to the JVM or native images.