Going serverless with Quarkus, GraalVM native images and AWS Lambda
Short version: In this talk, I'll show how I migrated the backend for the NLJUG conference app (used for J-Fall, J-Spring and more events) from Spring running on Linux virtual machines to Quarkus running as GraalVM native image on AWS lambda. Long(er) version: A conference app backend makes the ideal candidate for a serverless architecture: almost no traffic during the year, and peak traffic during conference days. In this talk, I'll show how I migrated the backend for the NLJUG conference app (used to rate talks for conferences with 1500+ attendees) from a traditional approach with Java and Spring running on Linux VM's to a fully serverless architecture with Quarkus, GraalVM native images, AWS lambda, API gateway and DynamoDB. I'll talk about (and demo) the Quarkus development experience, migrating code to Quarkus, creating native images and the caveats involved, testing, deploying to AWS with the SAM CLI, monitoring, costs and more. After this talk, you'll know enough to get started with building and deploying Quarkus native images on AWS Lambda yourself!
Recommended
Recommended
More Related Content
Similar to Going serverless with Quarkus, GraalVM native images and AWS Lambda
Similar to Going serverless with Quarkus, GraalVM native images and AWS Lambda (20)
Recently uploaded
Recently uploaded (20)
Going serverless with Quarkus, GraalVM native images and AWS Lambda
- 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. Serverless computing GraalVM & Quarkus Backend architecture About NLJUG & the NLJUG events app From Spring to Quarkus Experiences from running in production Wrap up & questions Outline W h a t ‘ s n e x t ? Demo! @bjschrijver
- 5. The NLJUG events app
- 6. NLJUG app: look & feel
- 7. NLJUG app: architecture AWS S3 Bucket App backend Internet Votes Content
- 8. NLJUG app: data flow User User App App S3 S3 Open app Get overall metadata List of all events Display all events Select event Get event metadata Event metadata (colors, link to event content) Get event content Event content (highlights, speakers, sessions) Show Event User User App App S3 S3 Open app Get overall metadata List of all events Display all events Select event Get event metadata Event metadata (colors, link to event content) Get event content Event content (highlights, speakers, sessions) Show Event User User App App S3 S3 Open list of sessions loop Get speaker image Speaker image Show session list
- 9. NLJUG app voting backend
- 10. App backend: first iteration (2015) AWS EC2 AWS ELB Wildfly 8 Java 7 Java EE Application AWS EC2 MySQL 5
- 11. 13
- 12. • 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/
- 13. My first serverless experience (2016)
- 14. App backend: second iteration (2018) AWS EC2 AWS ELB Spring Boot 2 Java 8 Spring Application AWS DynamoDB
- 15. 17
- 16. First serverless attempt (2019)
- 17. • 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
- 18. In the meantime…
- 19. • 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
- 20. Second serverless attempt (2022)
- 21. Third serverless attempt (2023)
- 22. Third serverless attempt (2023)
- 24. App backend: third iteration (2023) AWS Lambda AWS API Gateway GraalVM native image Java 17 Quarkus application AWS DynamoDB
- 25. Demo time!
- 26. Migrating from Spring to Quarkus
- 28. Migration: REST entity classes
- 30. Show me the code!
- 31. Experiences from running in production Photo: Dave Lehl
- 32. Monitoring, performance & scalability
- 33. Metrics during J-Fall 2023
- 34. Number of invocations per minute
- 35. Request duration (1 min avg)
- 36. Request duration (1 hour avg)
- 37. Success / error count
- 39. Logs
- 40. Costs
- 41. AWS costs for J-Fall 2023 app backend
- 42. AWS costs for J-Fall 2023 app backend
- 43. Is this the holy grail / graal?
- 44. • 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
- 45. Let’s wrap up!
- 46. • 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
- 47. 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!
- 49. Thanks for your time. Got feedback? Tweet it! All pictures belong to their respective authors @bjschrijver