Do Not Use Azure Functions with Java!
summary
Conclusion: Azure Functions with Java causes frequent runtime and developer friction: local debugging breaks on M1 Macs, the build-and-deploy process uses zipped artifacts that sometimes fail due to a deployment zip file lock, and observability and portal editing remain limited. Cold starts for Java measure 20–30 second cold starts unless using premium tier, and scaling forces waits (example: one instance handles ~10 req/min so 15 req/min triggers new instances and ~20s delays). Using Spring Native native images speeds startup but loses Java features.
AI-written summary · about
chapters (20)
- 0:00Introduction
- 4:03Help Ukrainian Refugees
- 5:49What are Azure Functions
- 8:20Cold Start vs Hot Start
- 9:42Azure Functions
- 10:28Why Azure Functions
- 12:23Azure Functions Dashboard
- 12:47Disadvantages
- 16:26How to deploy
- 17:35Summary
- 18:14Alternatives
- 19:24Bonus
- 21:33Questions
- 21:49Implementation
- 25:03Other languages
- 31:33Future of Java
- 34:48Microsoft Idea Integration
- 40:01Azure DevOps
- 41:30Logging
- 47:19Documentation
related talks
36mRunning Spring in a Serverless Environment
38mJava on Azure
34mThawing Java on AWS Lambda
51mAdapting Java for the Serverless world!
46mThawing Java on AWS Lambda Reducing Cold Start Times from 11 Seconds to 1
01h 03mCloud Cost Optimization for Java Developers
36mThe fast path to smart serverless with Spring Cloud Function & Azure Functions
55mLet’s Get Functional: The Fast Path to Smart Serverless