Fly like a rocket with Helidon
summary
Helidon 2.0 shows concrete gains: GraalVM native image support for both MP and SE, a CLI generator plus live-reloading dev loop, MicroProfile Reactive Streams and Reactive Stream Operators, and reactive Helidon DB Client and HTTP client. Measured quick-starts: native image memory ~28 MB (SE) and ~70 MB (MP); jlink images ~83 MB / 195 MB; plain JVM ~300 MB / 476 MB. Startup times: native nearly instant, MP native ~0.3 s, jlink SE ~0.3 s and MP ~1.5 s, JVM ~2.27 s.
AI-written summary · about
chapters (20)
- 0:00Start
- 6:04High Level Architecture of Heliodon
- 9:12Transparent no Magic
- 11:04Build Profiles
- 11:52J Link Image
- 13:38Memory Consumption
- 15:17Startup Time
- 19:02Micro Profile Implementation
- 20:13How Helidon Mk Supports Microprofile
- 21:42Microprofile Specs
- 22:46Health Check
- 26:55Fault Tolerance
- 28:21Open Api
- 29:49Demo
- 30:52Create a Project
- 35:02How a Development Loop Works
- 37:25Experimental Components
- 39:48Reactive Streams and Reactive Messaging
- 41:16Hidden Resources
- 45:20What's the Preferred Way To Build Spring Boot Applications
related talks
29mFly like a rocket with Helidon
31mFly like a rocket with Helidon
45mBuilding Cloud Native Services with Project Helidon
41mHelidon - Microservices on Modern Java
39mHelidon: Java Libraries for Writing Microservices
43mWhat's Coming in Helidon 4
49mRevolutionizing Microservices Development with Helidon 4!
45mVirtual Threads in the Real World: Fast, Robust Java Microservices with Helidon
