The document discusses using Quarkus, GraalVM, and AWS Lambda for serverless Java applications. It describes how the author previously implemented a backend application using Spring Boot and EC2, then migrated it to use Quarkus, GraalVM native images, and AWS Lambda. The migration process and some experiences running the application in a serverless configuration are covered. Some caveats of using GraalVM native images and Lambda are also mentioned, such as limitations on third party library support and difficulties with debugging.

1. bertjan@openvalue.eu
With Quarkus, GraalVM native images and AWS Lambda
Bert Jan Schrijver
Going serverless
@bjschrijver

2. Bert Jan Schrijver
L e t ’ s m e e t
@bjschrijver

3. About the NLJUG

4. The NLJUG events app

5. NLJUG app: look & feel

6. NLJUG app: architecture
AWS S3
Bucket
App backend
Internet
Votes
Content

7. NLJUG app voting backend

8. App backend: first iteration (2015)
AWS EC2
AWS ELB
Wildfly 8
Java 7
Java EE
Application
AWS EC2
MySQL 5

9. 9

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/

11. My first serverless experience (2016)

12. App backend: second iteration (2018)
AWS EC2
AWS ELB
Spring Boot 2
Java 8
Spring
Application
AWS
DynamoDB

13. 13

14. First serverless attempt (2019)

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

16. In the meantime…

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

18. Second serverless attempt (2022)

19. Third serverless attempt (2023)

20. Third serverless attempt (2023)

22. App backend: third iteration (2023)
AWS Lambda
AWS
API Gateway GraalVM
native image
Java 17
Quarkus
application
AWS
DynamoDB

23. Demo time!

24. Migrating from Spring to Quarkus

25. Migration: REST endpoints

26. Migration: REST entity classes

27. Migration: Other changes

28. Experiences from running in production
Photo: Dave Lehl

41. • 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

42. Let’s wrap up!

43. • Serverless Java is totally doable in 2024!
• Quarkus & GraalVM ❤ serverless
• Ideal for small/hobby projects
• As usual, YMMV ;-)
• Demo/seed project:
https://github.com/bertjan, repo:
quarkus-graalvm-aws-lambda-arm64
Summary

44. Source: https://cdn2.vox-cdn.com/thumbor/J9OqPYS7FgI9fjGhnF7AFh8foVY=/148x0:1768x1080/1280x854/cdn0.vox-cdn.com/uploads/chorus_image/image/46147742/cute-success-kid-1920x1080.0.0.jpg
THAT’S IT.
NOW GO KICK SOME ASS!

45. Questions?
@bjschrijver

46. Thanks for your time.
Got feedback? Tweet it!
All pictures belong
to their respective
authors
@bjschrijver