Configuration management for SaaS/BPaaS solutions
summary
Argues that vertical SaaS needs unified, central configuration rather than per-customer silos and shows a practical design: a central repository of baseline configs, configuration stacking where customers store only deltas, and a release model so customers point to new platform versions for one-click promotion. Tests and documentation inherit from the base, pipelines automate deployments, and manual migration steps are planned for data reprocessing; outcome reduces onboarding footprint, speeds regulatory updates, and keeps maintenance costs lower than per-customer customizations.
AI-written summary · about
chapters (6)
- 0:00Start
- 0:40Evolution of enterprise software business models
- 15:35Product development
- 21:10Extensibility
- 34:38Scalability & maintainability
- 38:15Organizational structure
related talks
29mLet's call platforms what they really are, ways to provide something-as-a-Service
40mPlatform Wars: The Battle Between Golden Paths and Spaghetti Pipelines
41mDesigning an Engineering org for SaaS & on-prem Delivery Models
39mCloud Configuration Ecosystem at Intuit
24mA Cloud Native Foundation For Developer/Application Platforms
43mStandardizing Microservice Development
24mFrom Kubernetes to PaaS to Developer Control Planes
48mCombating the struggles of modern cloud-native java developers