Google Site Reliability Engineering VS Enginered

Google Site Reliability Engineering mentions (84)

• Ask HN: What makes SRE great compared to "plain" DevOps?

  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 / 6 months ago

• How Site Reliability Engineering Is Different From DevOps

  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: 8 months ago

• API Product Managers, what's your workflow when designing and maintaining an API?

  Define SLOs for availability and latency. Google's SRE book is good reading for this. Source: 11 months ago

• Starting an SRE position soon. No prior experience (except IT). Any suggestions? Sorry if it's too general.

  Have you gone through the SRE Books? Source: 11 months ago

• Starting up with sre

  Google SRE books is always a good read. Source: 11 months ago

Enginered mentions (0)