Modern Java App Development in the Cloud
summary
Simple random-word Java service (noun + adjective) uses MicroProfile + Quarkus and a cloudbuild.yaml to build a container, push it to a registry, and deploy to Cloud Run serverless. Code requires no changes when switching app servers; deployment automates on git push. Measured cold starts show ~7s JVM cold-start versus roughly 3–4s native/GraalVM, so Quarkus native images cut startup time at the cost of longer build times.
AI-written summary · about
chapters (10)
- 0:00Modern Java cloud intro
- 1:49Cloud-native Java matters
- 6:19REST APIs with Jakarta EE
- 13:44MicroProfile creators
- 17:56Local code to cloud microservices
- 21:03Automating cloud builds
- 25:41Deploying with Cloud Run
- 33:04Quarkus startup times
- 37:16Native images for speed
- 40:08JVM vs native demo
related talks
46mModern Java App Development in the Cloud
51mModern Java App Development in the Cloud
34mModern Java App Development in the Cloud: MicroProfile, Quarkus, and Cloud Run
47mJava App Development in the Cloud: MicroProfile, Quarkus and Cloud.
47mServerless Java Apps in the Cloud: Microprofil, Quarkus & Cloud Run
40mServerless Java Apps in the Cloud
53mServerless Java #slideless
55mQuarkus brings Serverless to Java developers
