Configman - the grand unified theorem of configuration
summary
Configman provides a single API that overlays any key/value mapping sources (defaults, files, env, CLI) and supports dynamic class/module loading so configuration can instantiate classes, choose DB drivers, or return live objects like DB connections. It acts as an inadvertent dependency injection framework, powers Socorro at Mozilla processing 3–5 million crashes/day, and lets teams swap storage backends (HBase to Ceph) or add components rapidly (SAP module done in two days). Complexity shifts into config and demands rigorous integration testing.
AI-written summary · about
chapters (19)
- 0:00Start
- 5:11Getting Config into a Program
- 6:51A Digression...
- 7:29white white white white white
- 7:40blue white blue blue white
- 7:54green white yellow yellow green
- 8:11green white yellow orange orange
- 8:28application defaults
- 8:39command line
- 24:39Option Options
- 26:33the configuration object
- 28:53Three Part Design
- 29:40Socorro Collector
- 30:15Socorro Crashmover
- 31:04Socorro Processor
- 31:31Socorro Middleware
- 31:56Socorro is...
- 32:51Configman Benefits
- 33:50Configman Downsides
related talks
18mMobileConfig: Remote Configuration Management for Mobile Apps at Hyperscale
40mConfiguration Management Initiative 2.0 updates
18mEverything-as-Code: It's time to fix configurations
32mConfiguration Is (riskier than?) Code
47mCuttlefish Easing the Pain of Configuration
21mConfiguration Languages Are the Bane of Our Existence
45mConfiguration management for SaaS/BPaaS solutions
24mUsing Declarative Configs for Maintainable Reproducible Code