Defusing the configuration time bomb with PureConfig and Refined
summary
Research shows 75% of high-severity failures trace to latent configuration errors; real incidents include App Engine’s 2010 outage after a manual config edit and long-delayed job failures from invalid retention settings. The solution demonstrated uses PureConfig to load HOCON into typed case classes and Refined to enforce constraints at load time (non-empty API keys, positive durations, UUID regex, port range 1024–65535, writable-directory checks), plus a simple pre-start validator that fails fast so latent “time bombs” are detected before jobs run.
AI-written summary · about
chapters (11)
- 0:00Intro
- 0:54Algorithm analogy
- 3:10Configuration Errors
- 6:40Research
- 7:56What can we do
- 9:09Real code
- 11:51Indirection
- 13:32Hakan
- 19:03Refined
- 26:03Tips
- 30:39Questions
related talks
46mPoka Yoke Mistake proofing via Functional Programming
36mYou Might Just be a Functional Programmer Now
52mDestructuring the Enterprise
39mAn API refined over 18 months
16mScale By The Bay 2018 Unconference: Gabriel Volpe
31mBuilding a Sustainable CodeBase with FP
01h 03mNon-Functional Coding
30mCONQUERING CONCURRENCY WITH FUNCTIONAL PROGRAMMING