Spring, Quarkus, Jooby, Vert.x: Which Fits Your Architecture?

The cheapest Java framework on day one can become the most expensive by year two. Spring Boot, Quarkus, Jooby, and Vert.x can all build Java services — but they optimize for very different things. Some give you enterprise conventions and hiring safety. Others give you faster startup, smaller images, or more explicit control. And some move more architectural responsibility onto your team. We compare them across nine criteria: architecture fit, dev speed, ecosystem, code complexity, memory footprint, maintenance cost, stability, performance model, and hiring risk — using the same demo domain across all four. You'll see where Spring Boot remains the safest enterprise default, where Quarkus fits cloud-native Java, where Jooby makes sense for lean services, and why Vert.x is a reactive toolkit — not just "Spring, but faster." Container images are built with BellSoft hardened Liberica runtime containers. We compare image size, build time, startup time, and lines of code as an untuned JVM baseline — no AOT, no GraalVM Native Image. No universal winner — just the trade-offs that matter before the framework becomes your technical debt. Link to the demo: https://github.com/code-with-bellsoft... 00:00 — Framework War → Decision Map 00:24 — The Decision Framework 01:29 — Spring Boot 03:22 — Quarkus 05:53 — Jooby 08:14 — Vert.x 10:49 — Benchmarks & Decision Matrix 12:13 — Recap / Next Steps