Spring Framework: The Ultimate Configurations Battle!
summary
Three demo-only configurations for the same small app: XML, Java @Configuration, and Groovy are implemented and exercised with live coding demos; a REST endpoint parses payloads (XML and JSON) and writes results into Hazelcast maps. The talk shows concrete fixes: scope choices (singleton vs prototype vs request), method lookup injection to create new parser instances per use, proxying to refresh request-scoped beans, and intermittent live-demo failures that get debugged on stage. Groovy enables hot-reload Groovy scripts to swap parser behavior without redeploy, and audience applause voting repeatedly favors Java for clarity but highlights no single silver bullet.
AI-written summary · about
chapters (10)
- 0:00Introduction and setup
- 4:44Project overview
- 8:48Hazelcast instance configuration
- 14:41Solving state management issues
- 25:43Handling multiple data inputs
- 37:20Switching data formats to JSON
- 43:28Environment-based configurations
- 51:45Externalized configuration management
- 58:55Dynamic configuration updates
- 1:11:52Conclusion and final thoughts
related talks
01h 20mSpringOne2GX 2012 Keynote Day 1: Spring 2012 and Beyond
05h 30mDay 2
46mSpring Boot under the hood
44mLittle Treasures: The Useful Spring Classes That You Might Not Know
49mMagical Beans and Mystery
01h 34mBoot yourself, Spring is coming
51mBrewing the Best of All Worlds
43mInside Spring: The Architecture Behind the Framework