Java and Jakarta EE applications can run on Nanos Unikernel without any code changes or JVM modifications, enabling a simpler and more efficient deployment model. A proof of concept demonstrates Quarkus with IBM Semeru Runtime deployed as a unikernel image on AWS Graviton2 (ARM64) via the Nitro hypervisor. The unikernel stack eliminates the guest OS and container runtime layers, reducing boot time, memory footprint, and attack surface. The same Nanos image previously run on Oracle Cloud Infrastructure was deployed unchanged on AWS, confirming hypervisor and cloud-provider independence. The PoC is fully reproducible via a public GitHub Actions workflow.
Table of contents
The Cloud Evolves and Meets Unikernels: Java and Quarkus on ARM64 AWS Graviton with Nanos UnikernelJava and Jakarta EE Truly Meet UnikernelsFrom Virtual Machines and Containers to UnikernelsProof of Concept OverviewArchitectural Diagram of the PoCContainers vs Unikernels: A Stack ComparisonQuarkus, Semeru, and Nanos on AWS Nitro GravitonAWS Nitro: Cloud-Native Capabilities Without KubernetesHypervisor IndependenceWhy This Matters for Java and Jakarta EEConclusionSort: