Java Particle Acceleration using Quarkus
summary
Quarkus claims to cut Java cloud footprint dramatically: typical cloud stack uses ~220 MB, Quarkus on JVM ~130 MB and GraalVM native ~35 MB, with boot+first-request times dropping from ~9s to ~0.14–0.55s. Demos use Maven, Docker, GraalVM, MariaDB, OpenAPI/Swagger and show live reload updating code and DB schema without restart. Persistence uses Panache active record and generated Kubernetes manifests allow rapid replication — the demo runs ~100 instances locally, proving it works.
AI-written summary · about
chapters (11)
- 0:00Start
- 2:47Why Doing Things in Java
- 4:17Dynamic Class Loading
- 5:29Lazy Initialization
- 10:39Cost of a Java-Based Web Application
- 13:24Live Reload
- 18:57Ahead of Time Compilation
- 29:20Create Persistence Code
- 33:40Configure All the Database Connections
- 38:41Add a New Attribute
- 42:45Wait Error
related talks
48mSupersonic, Subatomic Java with Quarkus
52mQuarkus Supersonic Subatomic Java
55mQuarkus brings Serverless to Java developers
42mKeynote: Subatomic Java Microservices with Quarkus
45mFaster, greener, and happier- why Quarkus should be your next tech stack
30mSupersonic Java Quarkus with Knative serverless
49mQuarkus, the Java Stack back from the Future
54mQuarkus: Java development turned into delight