Keynote
summary
History of frameworks from Struts and Rails to Grails, Spring Boot and Micronaut frames why microservices exist, then drills into concrete tradeoffs: containers enable per-service units but startup time and memory drive cloud cost, Quarkus targets native performance via Quarkus + GraalVM native images at the cost of reflection limitations, Micronaut reduces runtime overhead by moving DI to compile time, and Go remains the baseline for smallest footprint. Operational needs—tracing and federation become mandatory—and monitoring, deployment size and latency determine whether a pile of services actually works.
AI-written summary · about
chapters (13)
- 0:00Introduction and keynote setup
- 1:45History of Java frameworks
- 7:48From monoliths to microservices
- 12:48Containers and microservices design
- 16:26Hidden costs of microservices
- 17:08Lightweight Java frameworks
- 19:59MicroProfile and alternatives
- 23:32Micronaut and Quarkus revolution
- 28:09Go vs Java performance
- 29:16Monitoring and tracing microservices
- 32:11Open source contribution realities
- 36:50Commercial vs open-source tools
- 37:31Closing and key takeaways
related talks
30mBattle Of The Microservice Frameworks: Micronaut versus Quarkus edition!
42mKeynote: Subatomic Java Microservices with Quarkus
23mLightning Talk: Rethinking Microservices
01h 12mArchitecting and delivering Java applications in the cloud era
45mFaster, greener, and happier- why Quarkus should be your next tech stack
47mJava App Development in the Cloud: MicroProfile, Quarkus and Cloud.
01h 10mEnterprise Java on Steroids
54mEnterprise Framework Battle: Quarkus vs. Spring Boot