2. Topics / Agenda
1
Why & What is DevOps?
2
SRE
3
Relation between SRE & DevOps
4
SRE Details
3. What is DevOps? - AWS
DevOps is the combination of cultural philosophies, practices, and tools that increases
an organization's ability to deliver applications and services at high velocity: evolving
and improving products at a faster pace than organizations using traditional software
development and infrastructure management processes. Ref
4. Why DevOps? ● To align on the mindset and
activities which speeds up
software delivery
● Reduce Human Errors
● Consistency (because code)
● Reduce manual efforts
5. How to DevOps?
*Generally
via DevOps Principles
● Have CICD practices
● Shift Left
● Continuous Improvements
● Remove Silos
● Automate
● Shared Responsibilities
● Autonomous Teams
10. ● Non Competing
● Class SRE Implements Interface DevOps
https://goo.gl/CKv3tV
● SRE is part of whole DevOps Umbrella
○ SRE defines the practices which DevOps
suggests
○ And MORE
SRE vs DevOps
11. SRE Details
SLI
Service Level Indicator
Availability, Throughput, Error
Rate
SLO
Service Level Objectives
E.g.: 99% availability
Error Budget
the amount of error that your
service can accumulate over a
certain period of time.
Tolerance of user happiness
12. SRE Practices
● Remove Toil
● Defining criticalities (System, downtime, unavailability)
● System Designing (DR, Multi or Poly Cloud, Multi-Region Deployments)
● Observability
● Chaos Engineering
13. SRE Practices
● ONLY people who can touch Production Environment
● MTTR, MTBF
● Incident Management
● Postmortems
Notas do Editor
We define toil as mundane, repetitive operational work providing no enduring value, which scales linearly with service growth
A complex system that works necessarily evolved from a simple system that works. Simplicity, goes into this topic in detail