10. • Functions-as-a-service (FaaS)
• Short running
• Small units of execution
• On demand, pay per use, scale to zero
• Startup time matters (for cold starts)
• There are still servers ;-)
Serverless computing
Background source: https://filmquarterly.org/2012/07/02/i-robot-what-do-robots-dream-of/
15. • JDK & JVM
• Built by Oracle
• Two runtime options:
• run as JVM (Based on Hotspot) with JIT
• ahead-of-time compilation to platform-
specific native image binary
GraalVM
17. • Kubernetes native web framework
• Open source, developed by Red Hat
• Designed to work with Java ecosystem
• Tailored for OpenJDK HotSpot and
GraalVM
• Great developer experience
Quarkus
42. • Cross compiling across cpu architectures is slow
• 3rd party library support for native images is not
guaranteed (but Quarkus libs are good)
• Reflection and native images can be tricky
• Debugging can be painful if problem is not local
• You need limits on lambda and API GW
• Probably good to use build & deploy pipelines ;-)
Quarkus/GraalVM native/Lambda caveats