Service Ownership: DevOps for Salesforce
summary
Salesforce shifts from a NOC-driven model to development service ownership, putting ownership of monitoring, alerts, releases, change and capacity into product teams while using a hybrid handoff to SRE/Infra as a Service for 24/7 ops. The platform handles 1.1 trillion transactions per year and absorbs acquired stacks like Commerce Cloud and ExactTarget, forcing tooling and runbook standardization; change volume rises sharply — roughly a tenfold increase in change rate — driving a pragmatic service ownership maturity model.
AI-written summary · about
chapters (14)
- 0:00Introduction
- 0:25Ray and Martin introduction
- 2:10Data proliferation
- 3:10Velocity of growth
- 4:55Customer experience
- 7:20Getting started
- 9:08Service definition
- 10:02Why service ownership
- 11:53Operational model
- 12:12Monitoring team
- 13:49Solutions management
- 16:58Capacity management
- 20:12The schism
- 24:32Wrap up
related talks
32mA Peek Inside the Enterprise Cloud at Salesforce
13mChaos Engr. and Service Ownership at Enterprise Scale
07mDevOps for Salesforce and Other Low-code Platforms
28mDevOps in the Enterprise: A Transformation Journey
20mHow AWS infrastructure addresses Salesforce’s resiliency goals
30mService Ownership @Slack
29mDOES14 - Reena Mathew and Dave Mangot - Salesforce
44mFull Service Ownership & The Lifecycle of a Service