Points to remember

The following are some important points:

• If DevOps is a philosophy, SRE is a prescriptive way of achieving that philosophy: class SRE implements DevOps.
• SRE balances the velocity of development features with the risk to reliability.
• SLA represents an external agreement and will result in consequences when violated.
• SLOs are a way to measure customer happiness and their expectations.
• SLIs are best expressed as a proportion of all successful events to valid events.
• Error budget is the inverse of availability and depicts how unreliable a service is allowed to be.
• Toil is manual work tied to a production system but is not the same as overhead.
• The need for unifying vision, communication, and collaboration with an emphasis on blameless postmortems and the need to encourage psychological safety and reduce resistance to change are key SRE cultural practices.
• Google emphasizes the use of microservices and cloud-native development for application development.
• Serverless services are managed but managed services are necessarily not serverless.