A day in life of a Quarkus developer
summary
Live-coded creation of a Quarkus app using the quarkus CLI shows dev mode with hot-reload typically under 800 ms, continuous testing that reruns relevant or failed tests automatically, and a browser Dev UI for inspecting beans; the ecosystem lists ~1000 extensions and build-time trimming removes about 65 unused CDI beans. Automatic Dev Services spins up a Postgres container when a JDBC driver is added, and Hibernate Panache generates active-record style entities and REST endpoints on the fly.
AI-written summary · about
chapters (7)
- 0:00Quarkus developer life intro
- 1:25Starting Quarkus project
- 8:07Dev Mode and testing
- 15:07Dev UI and extensions
- 21:55Hibernate Panache DB
- 29:47Dev Services auto infra
- 34:44REST Data extension
related talks
52mA day in the life of a Quarkus developer
46m5 Ways to Make Java Development and Kubernetes Spark Joy With Quarkus.
37mQuarkus in Action…in Action!
49mQuarkus, the Java Stack back from the Future
55mWhy You Want to Code With Quarkus in 2023
51mQuarkus why, how and what
46mQuarkus why, how and what
53mMeet Quarkus