Java Patterns and Practices for Serverless Applications
summary
Shows how to ship Java serverless as one serverless archive ZIP containing a Quarkus HTTP entry (deployed as a Quarkus function URL) plus asynchronous Lambdas (S3/eventbridge listeners), all deployed with CDK in Java and reusable Maven-published constructs. Gives concrete cost math (roughly €7/month for a 1‑CPU Lambda at low load), startup numbers (multi‑hundred ms cold starts, 2s reported for large jars and halved with AWS SnapStart) and operational choices (provisioned concurrency ~€20/month, logging to CloudWatch, multi‑account per service).
AI-written summary · about
chapters (16)
- 0:00Introduction to serverless Java
- 2:08Cost-driven cloud architectures
- 6:01Energy efficiency of Java
- 17:31Microservices as Lambda functions
- 18:56Serverless archive pattern
- 23:12Infrastructure as Java code
- 27:48Reusable infrastructure constructs
- 31:21Structuring serverless infrastructure
- 34:53Deployment pipelines in Java
- 37:32Live demo of serverless archive
- 39:40Monitoring and tracing strategies
- 41:28Monolithic Lambda viability
- 43:15Cloud-agnostic infrastructure tools
- 45:00Lambda@Edge use cases
- 46:03Helidon vs Quarkus comparison
- 48:14Q&A and closing remarks
related talks
52mContainerless, Bloatless, YAML-less, Serverless Java #slideless
56mThinking in Serverless Java (Code)
01h 03mKeynote: Why The Future of Java in the Cloud is Serverless
53mDissecting Serverless Enterprise Java Applications #slideless
53mServerless Java #slideless
31mServerless Java in Action: Cloud Agnostic Design Patterns and Tips
53m"Serverless" Is What J2EE Was Meant To Be
48mJava in the Clouds: Pointless and Expensive or Productive and Must-Have?