Modern Java App Development in the Cloud
summary
A simple Java service (returns two random words) goes from code to production using MicroProfile, built into a container, CI-triggered Cloud Build, and deployed serverless on Google Cloud Run. Switching runtimes is pure config so moving to Quarkus native with GraalVM cuts cold-starts: JVM cold-starts take about 6 seconds here versus ~1 second for the native binary. Repository and multi-stage Docker examples are provided so the exact build files and Docker/CI steps are reproducible.
AI-written summary · about
chapters (14)
- 0:00Modern Java cloud development
- 1:50Deploy Java apps to cloud
- 7:48Jakarta EE and MicroProfile
- 14:09Choosing MicroProfile runtime
- 16:13Containerizing Java apps
- 18:21CI/CD for cloud deployments
- 22:15Serverless with Cloud Run
- 24:40When serverless fails
- 28:15Startup time with Quarkus
- 33:17Native compilation
- 36:07JVM vs native performance
- 40:47Project resources
- 43:31Legacy to cloud-native
- 44:56Q&A
related talks
51mModern Java App Development in the Cloud
42mModern 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
55mQuarkus brings Serverless to Java developers
30mSupersonic Java Quarkus with Knative serverless
