How do we help enterprise to adopt SRE and DevSecOps practices?
summary
Enterprise migration projects adopt a hybrid cloud container platform to run legacy apps in containers, add observability with Grafana + ELK + distributed tracing, and institute SRE-run CI/CD, SLO-based alerting and capacity planning. A real case shows traffic stable while latency spikes trace to a microservice doing a full table scan; adding an index drops response time sharply. The team builds multi‑site HA, automated remediation and an SRE ops chart that routes alerts to the right owner.
AI-written summary · about
chapters (16)
- 0:00Helping enterprises adopt SRE & DevSecOps
- 1:15Conflicts between development and operations teams
- 3:01DevSecOps & SRE conflict resolution
- 5:08Business value of DevSecOps & SRE
- 7:18Enterprise adoption pain points
- 9:04Capacity planning for adoption
- 10:07Platform design & observability
- 11:34DevSecOps automation & process
- 12:38Solid platform design for SRE
- 14:07Monitoring model implementation
- 16:35Dashboards & golden signals
- 18:26Trend analysis with historical data
- 19:29Alerting strategies
- 20:54Case study: problem isolation
- 23:06SRE in root cause analysis
- 24:50Key takeaways
related talks
30mIntegrating cloud native security into the SRE culture
31mIntegrating Cloud Native Security into the SRE culture
08mSRE and Healthcare Data Compliance
35mRole of SRE in DevSecOps
33mSecurity and SRE: Natural Force Multipliers
35mSRE for [cyber]security
47mHow the SRE fits into the DevSecOps World?
39mWhen SRE and Security Teams Meet to Face a Crisis