Quarkus why, how and what
summary
Quarkus is a Java stack that moves framework work to build time to cut RAM and boot time, demonstrated by a to‑do app using JAX‑RS, JSON‑B, PostgreSQL and Hibernate ORM + Panache for active‑record style persistence. Development uses live reload ~300ms with full dev mode and embedded tests; production can compile to GraalVM native ~50ms startups. Extensions auto-configure datasources and reflection metadata. Project shows rapid iteration: 42 releases 177 contributors, and typical production split is ~80% HotSpot, 20% GraalVM.
AI-written summary · about
chapters (25)
- 0:00Introduction
- 0:41What is Quarkus
- 2:43Quarkus demo
- 5:02Generating the app
- 6:14Demo
- 8:55Whats the magic
- 9:54Test annotation
- 10:40Todo resource
- 14:35Database configuration
- 16:55Search engine
- 20:44Swagger UI
- 22:20Microservices
- 23:55Why Microservices
- 24:47Why Java
- 27:04Why Quarkus
- 31:29APIs
- 31:46How Quarkus works
- 33:12Faster startup
- 34:06Augmentation phase
- 35:18Grall VM
- 38:12Quercus
- 39:38Eclipse MicroProfile
- 40:13Sebastian Blow
- 42:11V for Vendetta
- 44:21Questions
related talks
46mQuarkus why, how and what
49mQuarkus, the Java Stack back from the Future
52mQuarkus Supersonic Subatomic Java
11mAll about Quarkus
45mFaster, greener, and happier- why Quarkus should be your next tech stack
54mQuarkus: Java development turned into delight
48mWhy Quarkus Should Be Your Next Tech Stack: Faster, Greener & Happier
44mQuarkus: Supersonic Subatomic Java