Serverless Java Apps in the Cloud
summary
A tiny app returns one random adjective and one random noun as JSON, built with MicroProfile, packaged in a container via Google Cloud Build, and deployed to Google Cloud Run; it runs, scales to zero, supports traffic splitting, and exposes cold-start limits unless compiled to Quarkus native binaries which cut startup times drastically. The pipeline uses reproducible multi-stage Docker builds, CI on push, and the demo service — a random-word service — works end-to-end, showing tradeoffs between JVM and native modes and why Cloud Run plus MicroProfile minimizes ops while keeping predictable behavior.
AI-written summary · about
chapters (11)
- 0:00Start
- 4:50Running code
- 6:44Jakarta EE for microservices
- 12:41Write your logic, not boilerplate code
- 13:06Lightweight
- 13:43Interchangeable
- 19:38Containerize it!
- 22:46To the Cloud!
- 31:35When not to go serverless?
- 33:21Make it fast!
- 35:57And even faster!
related talks
47mServerless Java Apps in the Cloud: Microprofil, Quarkus & Cloud Run
51mModern Java App Development in the Cloud
47mJava App Development in the Cloud: MicroProfile, Quarkus and Cloud.
34mModern Java App Development in the Cloud: MicroProfile, Quarkus, and Cloud Run
46mModern Java App Development in the Cloud
42mModern Java App Development in the Cloud
53mServerless Java #slideless
52mContainerless, Bloatless, YAML-less, Serverless Java #slideless