Exploring Quarkus on JDK 17
summary
Quarkus on JDK 17 shows concrete upgrades: a small web app that consumes the Bored API with three endpoints, six tests running under continuous testing, uses sealed classes and records plus extended switch expressions, adds a Rest Client and a circuit breaker (75% failure ratio, 5s half‑open, 4 max retries). Build uses Jib without Docker daemon, image pushed to a registry and deployed to OpenShift sandbox; JVM image ~100+ MB, native images ~54 MB and ~30 MB.
AI-written summary · about
chapters (11)
- 0:00Start
- 1:56Why To Use Java
- 2:15Why Use Java 17
- 3:51Default Container Awareness
- 6:31What Are the Differentiators That Make Quark Is Great Especially with Java 17
- 11:06Demo
- 13:55Add the Open Api Extension
- 34:54Container Image Tag
- 40:08The Sample Project
- 40:26Does Quarkx Has a Similar Thing To Spring Initializer in Intellij or Only on Quarkx
- 40:53Ways of Instantiating Quarkx
related talks
49mQuarkus, the Java Stack back from the Future
46mQuarkus why, how and what
51mQuarkus why, how and what
48mSupersonic, Subatomic Java with Quarkus
54mQuarkus: Java development turned into delight
49mThe road to Quarkus. Why and what to look for
11mAll about Quarkus
46m5 Ways to Make Java Development and Kubernetes Spark Joy With Quarkus.