Spring Meets GemFire Meets Native: Take Your Spring Apps to the Next Level
summary
Spring Boot 3 + Spring Data for VMware GemFire replaces Postgres and doubles throughput from ~1,700 to ~3,400 orders/sec (JMeter, 300 simultaneous users) and then to ~5,500 req/sec when compiled as a GraalVM native image; startup drops from ~5s to 0.151 seconds in-cluster and to ~110–150ms locally, resident memory falls from ~420MB to ~110MB, and Gradle + Docker buildpacks plus native-image agent produce the AOT hint files needed to run on Tanzu Kubernetes Grid.
AI-written summary · about
chapters (10)
- 0:00Introduction and team
- 1:22Traditional web app architecture
- 13:35Database bottleneck in traditional apps
- 15:01Introducing VMware GemFire
- 21:19Demo replacing JPA with GemFire
- 31:13Scaling challenges and scale to zero
- 33:21Spring Native introduction
- 41:53Demo making app native compilable
- 54:14Summary and key takeaways
- 54:43Q&A session
related talks
47mGoing Native: Fast and Lightweight Spring Boot Applications with GraalVM
31mBring the action: using GraalVM in production
44mBring the Action: Using GraalVM in Production
51mMigrating Spring Boot apps to GraalVM
49mThe Path Towards Spring Boot Native Applications
46mNative builds with Spring Boot 3
12mWhat's new with Spring Native on Google Cloud
52mLean Spring Boot Applications for the Cloud