Thawing Java on AWS Lambda Reducing Cold Start Times from 11 Seconds to 1 | Daniel Raniz Raneland

Java has never been a perfect fit for Function as a Service platforms such as AWS Lambda or Azure Functions. While both platforms have official support for Java, Java functions unfortunately suffer from significantly longer cold start times than many other runtimes.

In this talk I will show a simple Spring Cloud Java function running on AWS Lambda with fairly horrible cold start times of around 11 seconds and then show how we can fix this by using GraalVM Native Image to perform most of the work during compile time. The end result is cold start times of less than a second, making Java a viable, though not without drawbacks, choice for FaaS platforms that support custom runtimes.

I will also compare this solution to Amazon's Lambda SnapStart to discuss the differences between the two solutions.

➜ Abonniere JAVAPRO und verpasse keine News:

▬ Über uns: ▬

JAVAPRO ist das Magazin für professionelle Java-Entwicklung in der Praxis.
Über das Magazin hinaus ist JAVAPRO Veranstalter der jährlich stattfindenden Entwickler-Konferenz JCON. Auf der JCON stehen Core Java, Enterprise Java, Microservices, APIs und Frameworks im Fokus.
Auf diesem Kanal finden sich Interviews, Sessions, Tipps & Tricks und alles, was das (Java)-Entwickler-Herz begehrt.

➜ Jetzt kostenlos Magazin anfordern:

▬ Folge uns auf Social Media: ▬

➜ Danke fürs Abo & fürs Zusehen!