On the Wings of SREs; J.P. Morgan's Journey into the Cloud
summary
J.P. Morgan Chase creates an SRE function to catalyze cloud migration across 57,000 technologists and a $14B annual tech budget, moving from under 100 to over 500 services in a few years. Challenges include regulatory controls, a heterogeneous stack (mainframes, FPGA, quantum, COBOL, many languages), shifting from incident counts to SLO-based reliability, building trust by embedding with teams (joining remote sprint planning, writing Terraform and observability code), and making resource and cost signals first-class.
AI-written summary · about
chapters (19)
- 0:00Intro
- 0:29Welcome
- 1:33Preface
- 2:55JP Morgans Journey into the Cloud
- 5:26JPMorgan Chase
- 6:57Compute Platforms
- 8:01Programming Languages
- 9:51What is SRE
- 10:27Challenges
- 11:42Resource Management
- 12:36Opex
- 13:24Measuring Reliability
- 14:10Managing Infrastructure
- 14:51Establishing Relationships
- 15:35How to Scale
- 16:10Building Trust
- 17:24You are an SRE
- 18:26Challenges of Scale
- 19:08Trust and Reliability
related talks
33mHow Our Continuous Delivery Platform Is Enabling the Public Cloud Migration Journey at JPMorgan Chase & Co.
18mSRE Engagement Model Transition in Building and Expanding SRE Team
13mWhat To Do When SRE is Just a New Job Title?
07mIterative Enterprise SRE Transformation
33mChallenges of Starting an SRE Team from Scratch in an Enterprise
41mBuilding an SRE Capability Inside a Large Organization
54mAccelerating innovation securely, featuring JPMorgan Chase
43mSRE From Inception to Global Scale