Scaling ops: Embracing platform engineering’s potential
summary
Platform engineering here means building small reusable IaC units rather than monolithic golden paths: golden blocks encapsulate single architecture pieces with baked-in dead-letter queues, least-privilege policies, alarms and monitoring. Engineers fill a JSON-schema front end that spits out a structured artifact for downstream tooling, while a single orchestrator runs provision pipelines, records audit-ready deployment history and creates inventory-backed cost breakdowns (example: $250/month saved by downsizing). Several open-source helpers are promised to implement these patterns.
AI-written summary · about
chapters (12)
- 0:00Introduction
- 0:37Why Platform Engineering
- 2:03Golden Blocks
- 3:27Lowering cognitive overhead
- 6:42Catalogs
- 8:11Orchestration
- 9:39Audit logs
- 10:13Inventory
- 11:00Staging vs Production
- 11:33Datadog
- 12:40Costs
- 14:08Conclusion
related talks
20mScaling DevOps Without Scaling Ops
25mFrom Ops to Impact: Scaling Engineering Velocity
40mPlatform Wars: The Battle Between Golden Paths and Spaghetti Pipelines
36mScaling Platform Engineering Without Slowing Developers Down
27mPortals and Platforms, Two Ps in a Pod? How Good Interfaces Make for Good Operability
44mPlatform Engineering is All About Product
27mTurning Platform Engineering Work Into Business Value Leadership Understands
43mEngineering Platforms Evolved