J-Spring 2024 - Going serverless with Quarkus, GraalVM native images and AWS Lambda

Presented at NLJUG's J-Spring 2024.

1. [email protected]
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. 11

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 computingBackground 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. 15

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. Show me the code!

29. Experiences from running in productionPhoto: Dave Lehl

30. Monitoring, performance & scalability

31. Metrics during J-Fall 2023

32. Number of invocations per minute

33. Request duration (1 min avg)

34. Request duration (1 hour avg)

35. Success / error count

36. Concurrent executions

37. Logs

38. Costs

39. AWS costs for J-Fall 2023 app backend

40. AWS costs for J-Fall 2023 app backend

41. Is this the holy grail / graal?

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

43. Let’s wrap up!

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

45. 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!

46. Questions?
@bjschrijver

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