> Markdown version of [/videos/1595-like-spring-but-faster-the-new-java-jedi?t=1215](https://www.wearedevelopers.com/videos/1595-like-spring-but-faster-the-new-java-jedi?t=1215). Every page supports `.md` or `Accept: text/markdown`. Links point to the HTML versions so they work for humans too. Agent guide: [/agents.md](https://www.wearedevelopers.com/agents.md). --- # Like Spring, but Faster: The new Java Jedi Slash cloud costs and memory footprints without abandoning your Java expertise. See how Quarkus shifts Spring Boot initialization to build-time for ultra-fast, Kubernetes-native deployments. - **Speakers:** [Eric Deandrea](https://www.wearedevelopers.com/@eric-deandrea) - **Event:** World Congress 2025 - **Published:** August 20, 2025 - **Duration:** 30:15 - **URL:** https://www.wearedevelopers.com/videos/1595-like-spring-but-faster-the-new-java-jedi ## Summary For decades, Java's "write once, run anywhere" philosophy relied on a heavyweight dynamic runtime, resulting in high memory overhead and protracted JVM warmup periods. While acceptable for monolithic architectures, this model severely restricts horizontal scaling in resource-constrained Kubernetes and container environments. Quarkus solves this bottleneck by shifting framework initialization—such as dependency injection assembly and dynamic proxy generation—from runtime to build time. By comparing a standard Spring Boot application to a Quarkus equivalent using identical source code, engineers can observe radical operational shifts. Because Quarkus extensions adapt Spring APIs to Jakarta standards during compilation, it natively behaves as an Ahead-of-Time (AOT) framework. Live benchmarking underscores that Quarkus drastically cuts the "time to first request" and Resident Set Size (RSS) memory footprints, empowering Java applications to handle higher throughput on significantly smaller compute instances. Further compiling applications into a GraalVM Native Image produces ultra-fast, lightweight binaries optimally tailored for serverless operations or edge devices. However, architects must navigate essential trade-offs, as traditional JVMs retain superior throughput for long-running deployments due to active JIT compiler optimizations and garbage collection. Embracing build-time optimization gives organizations the power to slash cloud infrastructure costs and improve carbon efficiency without abandoning entrenched Java expertise. **Keywords:** java runtime optimization, JVM warmup constraints, quarkus build-time compilation, spring boot auto-configuration, graalvm native image binaries, RSS memory footprint, time to first request benchmarking, AOT compilation, containerized java performance, kubernetes resource allocation, jakarta application standards, JIT compiler optimization, cloud infrastructure cost reduction, serverless java deployment, carbon efficient software ## Chapters 1. **Understanding Java virtualization and just-in-time compiler performance challenges** (00:00) — The historical design of Java runtime environments introduces heavy resource costs for initialization and dynamic compilation processes. 1. **Running traditional Java applications in constrained containerized environments** (04:02) — Deploying applications into constrained containers amplifies the negative impacts of traditional virtual machine startup overhead. 1. **Understanding Spring framework initialization and runtime configuration processes** (05:44) — Standard Spring auto-configuration mechanics incur significant computing delays during the dynamic runtime application assembly phase. 1. **Shifting Spring framework initialization to build time with Quarkus** (07:00) — Pre-computing framework behaviors and dependency chains at build time bypasses reflection penalties to drastically optimize startups. 1. **Removing JVM overhead to produce target-specific application binaries** (08:48) — Eliminating the virtual machine layer by compiling execution logic directly into native binaries significantly reduces system overhead. 1. **Benchmarking standard Spring Boot application initial request latency metrics** (10:34) — Establishing baseline infrastructure metrics reveals the standard memory footprint and initial request latency of legacy setups. 1. **Evaluating ahead-of-time compilation metrics for Spring context initialization** (14:03) — Generating ahead-of-time context elements shaves off runtime initialization delays and modestly reduces application heap requirements. 1. **Replacing standard Spring dependencies with optimized Quarkus extension libraries** (16:42) — Adapting Spring properties into build-time optimized capabilities ensures faster deployments without modifying the core domain logic. 1. **Comparing native GraalVM image throughput against traditional JVM instances** (20:15) — Leveraging native executable techniques exchanges long-running throughput optimization for immediate latency performance and smaller runtime footprints. 1. **Processing unmodified Spring stack components into native executable formats** (24:00) — Compiling code into rigid static binaries inherently breaks dynamically configurable properties normally handled by ephemeral containers. 1. **Improving Kubernetes cluster capacity planning and deployment carbon efficiency** (27:15) — Lowering cloud compute allocations directly minimizes continuous operational expenditure and strictly limits application carbon emissions. ## Related Moments - [Optimizing container workloads with Quarkus and lightweight JVMs](https://www.wearedevelopers.com/videos/89-development-of-reactive-applications-with-quarkus) (from "Development of reactive applications with Quarkus") - [Overcoming Java cold starts using the Quarkus framework](https://www.wearedevelopers.com/videos/243-serverless-native-java-with-quarkus) (from "Serverless-Native Java with Quarkus") - [Utilizing Quarkus for Kubernetes native Java](https://www.wearedevelopers.com/videos/123-get-started-with-securing-your-cloud-native-java-microservices-applications) (from "Get started with securing your cloud-native Java microservices applications") - [Deploying native Quarkus applications to a Knative cluster](https://www.wearedevelopers.com/videos/243-serverless-native-java-with-quarkus) (from "Serverless-Native Java with Quarkus") - [Introduction to developer joy and the Quarkus ecosystem](https://www.wearedevelopers.com/videos/1591-developer-joy-with-quarkus) (from "Developer Joy with Quarkus") - [Creating and configuring a basic native Quarkus application](https://www.wearedevelopers.com/videos/243-serverless-native-java-with-quarkus) (from "Serverless-Native Java with Quarkus") ## Related Articles - [Top 10 Java Libraries](https://www.wearedevelopers.com/magazine/364-top-10-java-libraries) - [Using Java 17 latest features in real world projects](https://www.wearedevelopers.com/magazine/121-using-java-17-latest-features-in-real-world-projects) - [Dev Digest 121 - AI goes offline](https://www.wearedevelopers.com/magazine/456-dev-digest-121-ai-goes-offline) - [The Best JavaScript Framework to Learn](https://www.wearedevelopers.com/magazine/229-the-best-javascript-framework-to-learn) ## Related Jobs - [Java Softwareentwickler - Spring Boot & Microservices](https://www.wearedevelopers.com/jobs/ext/1306817-java-softwareentwickler-spring-boot-microservices) at **Aok Systems Gmbh** - [Senior Backend Engineer (Java)](https://www.wearedevelopers.com/jobs/ext/19369-senior-backend-engineer-java) at **Bonial International GmbH** - [Senior Software Developer Java (m/w/d)](https://www.wearedevelopers.com/jobs/39654-senior-software-developer-java-m-w-d) at **Sopra Steria Custom Software Solutions GmbH** - [Platform Engineer - Mercury Runtime Platform](https://www.wearedevelopers.com/jobs/ext/293235-platform-engineer-mercury-runtime-platform) at **Raiffeisen Bank International AG** - [Softwareentwickler Java](https://www.wearedevelopers.com/jobs/ext/1245896-softwareentwickler-java) at **Aok Systems Gmbh** - [(Senior) Java Software-Entwickler](https://www.wearedevelopers.com/jobs/48140-senior-java-software-entwickler) at **Finanz Informatik**