Quarkus

Quarkus
Name	Quarkus
Developer	Red Hat
Initial release	2019
Repository	GitHub
License	Apache License 2.0
Programming language	Java, Kotlin, Scala
Platform	Java Virtual Machine, GraalVM, HotSpot
Website	quarkus.io

Quarkus is a Kubernetes-native, open-source framework for building cloud-native applications optimized for containerized and serverless environments. It targets the Java ecosystem while integrating with technologies such as GraalVM, OpenJDK, Kubernetes, Docker, and Eclipse MicroProfile to reduce startup time and memory footprint for microservices, functions, and reactive systems. Quarkus was created and is maintained by Red Hat engineers as part of broader efforts to modernize Java for cloud platforms like OpenShift and Amazon Web Services.

History

Quarkus was announced in 2019 by Red Hat during events involving communities like Devoxx, Red Hat Summit, and KubeCon. Its development drew on prior work in projects such as WildFly, Vert.x, Spring Framework, Eclipse MicroProfile, and GraalVM to reconcile Java’s enterprise features with container constraints emphasized by Docker and Kubernetes. Early adopters included organizations working with OpenShift, Google Cloud Platform, Amazon Web Services, and Microsoft Azure, while contributors came from companies like IBM, Oracle Corporation, Payara, and community members active in GitHub and the Apache Software Foundation-aligned ecosystems. Over time Quarkus incorporated integrations with standards and projects such as Jakarta EE, Spring Boot, Hibernate ORM, Apache Kafka, and Prometheus.

Architecture and Design

Quarkus’s architecture centers on build-time processing, runtime optimizations, and native-image compilation. The design leverages build-time augmentation derived from experiences in WildFly and JBoss modules, and integrates with compile-time tools like GraalVM native-image and Maven and Gradle build systems. Runtime modes include JVM mode on OpenJDK and native mode via GraalVM to achieve low memory usage and fast startup for orchestration platforms such as Kubernetes and OpenShift. It provides extension points for frameworks like Hibernate ORM, Vert.x, Spring Framework, Eclipse MicroProfile, and Quarkus Extension mechanisms maintain modularity and align with library ecosystems including Jackson, Netty, and Apache Camel.

Features

Quarkus bundles a spectrum of features focused on cloud-native Java: live coding and fast reload support influenced by tools like JRebel and Spring Boot DevTools; built-in integrations with Hibernate ORM, JDBC, Apache Kafka, RESTEasy, gRPC, Micrometer, and OpenTracing/OpenTelemetry; first-class support for reactive programming via Vert.x; and compatibility layers for Spring Framework to facilitate migration. Observability features include metrics export to Prometheus and tracing compatibility with Jaeger and Zipkin. Quarkus also supports native-image produced with GraalVM to enable serverless deployments on platforms such as AWS Lambda and Google Cloud Functions.

Development and Tooling

The Quarkus developer experience integrates with IDE ecosystems including Eclipse IDE, IntelliJ IDEA, Visual Studio Code, and command-line tools like Maven and Gradle. Live coding is implemented through a developer mode that mirrors experiences in Spring Tools and JRebel, while extensions simplify wiring for databases, messaging, and observability using community-driven artifacts hosted on Maven Central and GitHub. Containerization workflows align with Dockerfile generation and buildpacks from Cloud Native Buildpacks, and CI/CD pipelines commonly employ systems like Jenkins, GitLab CI, GitHub Actions, and Tekton for automated testing and deployment to Kubernetes clusters managed by Argo CD or Flux.

Performance and Benchmarking

Performance goals emphasize reduced cold-start latency and lower resident set size compared with traditional Jakarta EE and Spring Boot applications. Benchmarks often compare Quarkus running in JVM and native modes against Spring Boot, Micronaut, Helidon, and WildFly, focusing on metrics such as startup time, memory consumption, throughput, and latency under load-generators like wrk and Gatling. Native-image results using GraalVM typically show significant improvements in startup time and memory footprint, making Quarkus suitable for serverless platforms and high-density container deployments on infrastructures from Amazon Web Services and Google Cloud Platform.

Adoption and Use Cases

Quarkus is adopted by enterprises and startups for microservices, event-driven systems, serverless functions, and edge computing use cases. Industries represented include finance with firms using Apache Kafka pipelines, telecommunications deploying on Kubernetes clusters, and e‑commerce platforms integrating with Redis and relational databases via Hibernate ORM. Cloud providers, platform vendors, and system integrators such as Red Hat, IBM, Oracle Corporation, and consulting firms have produced reference architectures and quickstarts for OpenShift, AWS Lambda, and Google Kubernetes Engine.

Security and Configuration

Security features in Quarkus integrate with standards and products such as OAuth 2.0, OpenID Connect, Keycloak, JWT, and cryptographic providers from Bouncy Castle and OpenSSL through platform integrations. Configuration is managed through a unified system inspired by patterns in Spring Framework and MicroProfile Config, with environment-specific overrides for cloud platforms like Kubernetes and OpenShift and secrets management via HashiCorp Vault and AWS Secrets Manager. Runtime hardening and vulnerability management are performed using static analysis tools and scanners common in DevSecOps pipelines including OWASP Dependency-Check, Snyk, and SonarQube.

Category:Java frameworks