Red Hat build of Quarkus

Why Red Hat build of Quarkus?

Traditional Java doesn’t fit cloud. Spring Boot is 300MB memory and 10s startup. Serverless cold starts too slow. Container density low. Cloud bills rising.

Red Hat build of Quarkus is Kubernetes-native Java for cloud-native applications. 10ms startup - serverless ready. 50MB memory - container density. GraalVM native compilation - near-native performance. Developer joy - live coding.

How does it work?

Build-Time Processing

Moving work to build:

• Metadata processing
• Reflection removal
• Bytecode generation
• Dependency injection
• Smaller runtime

GraalVM Native

Native compilation:

• Ahead-of-time
• No JVM overhead
• Fast startup
• Low memory
• Single executable

Extension System

Modular architecture:

• Optimized extensions
• Popular integrations
• Custom extensions
• Build-time optimization
• Ecosystem compatibility

Key Features

Developer Experience

• Live coding
• Hot reload
• Dev services
• Continuous testing
• IDE integration

Cloud-Native

• Kubernetes integration
• Health checks
• Metrics (Micrometer)
• Tracing (OpenTelemetry)
• Configuration

Framework Support

• RESTEasy (JAX-RS)
• Hibernate ORM
• Kafka clients
• gRPC
• Reactive streams

Performance Comparison

Metric	Quarkus Native	Traditional Java
Startup	~10ms	~5-10s
Memory	~50MB	~300MB
Density	10x+	baseline

Use Cases

Serverless Functions:

• AWS Lambda
• Azure Functions
• Google Cloud Functions
• Knative

Microservices:

• Container efficiency
• Fast scaling
• Cost optimization
• High density

Event-Driven:

• Kafka consumers
• Message processing
• Reactive systems
• Stream processing

Specifications

Language	Java, Kotlin, Scala
Compilation	JVM, GraalVM native
Standards	MicroProfile, Jakarta EE
Deployment	Container, serverless, VM

Who is it for?

• Java teams moving to cloud-native
• Serverless function developers
• Microservices architects
• Cloud users caring about costs

Benefits

For developers: Live coding, fast feedback, preserved Java skills

For operations: Lower memory, faster scaling, higher density

For business: Lower cloud costs, serverless capability

FAQ

Can I use existing Java code? Yes. Standard Java, Jakarta EE, MicroProfile compatible.

What is live coding? Instant reload on save. No restart.

Do I have to use GraalVM native? No. JVM mode also available. Native = maximum performance.

What extensions are available? 400+. Hibernate, Kafka, REST, gRPC and more.

How is the learning curve? Familiar for Java developers. Standard APIs.

Does it support reactive? Yes. Mutiny reactive framework built-in.

How does it integrate with OpenShift? Native integration. S2I, health, metrics.

What is support? Red Hat support. LTS releases.

Is it production-ready? Yes. Major enterprises in production.

How does support work? Red Hat support. nFlo offers Quarkus training and architecture.