In my view it is having a dedicated team focusing their full mental bandwidth on pro-actively understanding and managing robustness of the system. In Pure DevOps, it seems to me developers often don't have the full picture of the system, and not enough bandwidth to foresee complex interactions from their changes. These are from my experiences spending one year as a developer in somewhat large a greenfield... - Source: Hacker News / 7 months ago

Site Reliability Engineering, introduced by Google, extends the principles of software engineering to operations. Unlike DevOps, SRE places a stronger emphasis on reliability, availability, and scalability. SRE teams are tasked with maintaining the health and performance of systems by applying engineering practices to operations. The ultimate objective is to achieve a balance between service reliability and... Source: 10 months ago

Define SLOs for availability and latency. Google's SRE book is good reading for this. Source: about 1 year ago

Have you gone through the SRE Books? Source: about 1 year ago

Google SRE books is always a good read. Source: about 1 year ago

I think the reputable courses are purelyfunctional.tv, https://www.learnreframe.com/ , https://lambdaisland.com/. Some of them do have free content that will get you enough traction to get moving. Source: over 2 years ago

Https://purelyfunctional.tv/ is pretty good. The author is currently working on a new version of his courses. - Source: Hacker News / about 3 years ago