Ops in the Time of Serverless Containerized Webscale
summary
Argues that platforms like Cloud Foundry reduce friction but do not eliminate human failure modes, so teams must build guardrails, version-control every change, and instrument for capacity and debuggability; recommends on‑call rotation ownership instead of dumping devs into pager duty, and treating day one is short day two is forever as an operational mandate. Recommends observability and telemetry (mentions PCF metrics and the Honeycomb.io PCF tile), ties autoscaling and AWS realities to concrete monitoring and escalation practices.
AI-written summary · about
chapters (7)
- 0:00Introduction and background
- 2:46Human challenges in platform adoption
- 8:33Microservices and organizational incentives
- 15:56Observability and platform telemetry
- 22:13Tools vs. collaboration in DevOps
- 27:53Human factors in distributed systems
- 30:24Day two operations and architecture
related talks
35mHow to Cloud Ops Like a Boss
50mCracks in the Foundation: Operating Cloud Foundry...
39mPlatform Engineering as a (Community) Service
24mCracks in the Foundation: Operating Cloud Foundry in the Real World
47mDevOps is for Product Engineers, too.
40mDevOps in the era of serverless computing
30mThis is Not a Technology Problem: Leveraging Culture and Process to Make the Most...
14mKeynote: Open Source & Operational Excellence