Why Quarkus Should Be Your Next Tech Stack: Faster, Greener & Happier
summary
Quarkus claims dramatic runtime and cost wins: JVM startup as low as ~20 ms, GraalVM native builds (about a minute) give very high deployment density and native processes using ~10% of traditional memory; measured throughput shows Quarkus JVM ~9,000 rps vs Spring Boot ~7,000 rps and Quarkus Native ~3,000 rps at 48 concurrent connections. Tooling demonstrated includes GraalVM native compilation, Panache/Hibernate, Testcontainers for auto-spawned dev databases, and continuous testing; experiments report roughly half the carbon footprint versus a legacy stack.
AI-written summary · about
chapters (17)
- 0:00Intro
- 0:28History
- 3:55Java
- 7:13Quarkus
- 9:50Demo
- 12:09Faster than a lightbulb?
- 15:23Memory footprint
- 17:41Response time
- 19:49Dynamism
- 23:23Performance
- 25:00Demo
- 40:40Continuous testing
- 42:43Examples
- 43:04What about Spring?
- 44:24One last thing
- 47:02tl; dpa
- 47:22Outro
related talks
45mFaster, greener, and happier- why Quarkus should be your next tech stack
51mQuarkus why, how and what
44mQuarkus: Supersonic Subatomic Java
49mQuarkus, the Java Stack back from the Future
59mQuarkus for Spring Developers
11mAll about Quarkus
52mQuarkus Supersonic Subatomic Java
42mKeynote: Subatomic Java Microservices with Quarkus
