Let Devs Be Devs: Abstracting Compliance + Reliability to Accelerate JPMCs Cloud Deployments
summary
JPMorgan Chase builds a centralized platform that codifies app blueprints into Terraform scripts, wires those into the standardized CI/CD pipeline, and pre-enables an agent-based Gremlin integration so teams get deployments under an hour with embedded controls (security and compliance checks) enforced at deploy time. The productized chaos experiments run in test/dev and hyperscale public cloud environments, report automated RTO/RPO validations and alerts, and drive a roughly 10x recent adoption increase across a 6,000-app, 50,000-engineer estate.
AI-written summary · about
chapters (19)
- 0:00Introduction and speaker intro
- 1:06Enterprise scale at JPMorgan
- 2:31Challenges in modernizing tech stacks
- 3:36Goal for developer deployments
- 4:39Building centralized products
- 5:42Assembling compliant blueprints
- 7:08Introducing chaos engineering
- 8:55Standardizing resiliency services
- 10:58Resiliency validation and automation
- 13:04Key takeaways and conclusion
- 15:09Q&A session begins
- 15:51Culture of chaos engineering
- 19:03Defining resiliency requirements
- 21:13Cloud architecture and testing environments
- 23:00Chaos engineering across clouds
- 24:46Coordinating large-scale experiments
- 26:32Technology stacks for blueprints
- 28:58Modular blueprint system
- 30:23Closing remarks and team thanks
related talks
33mHow Our Continuous Delivery Platform Is Enabling the Public Cloud Migration Journey at JPMorgan Chase & Co.
54mAccelerating innovation securely, featuring JPMorgan Chase
12mContinuous Deployment in a heavily regulated environment
11mCD Demands Continuous Testing: Why We Built a Testing Platform Layer on ECS Usin...
20mUsing OPA to Ensure Compliant Software Delivery in a Highly Regulated Finance Envi...
29mCompliance At Scale: Hardened Terraform Modules at Morgan Stanley
27mWhy we provisioned 37 Jenkins servers...
28mScale Your DevOps Initiative Beyond Its Awkward Teenage Years
