DevOps vs SRE

 1. Reduce Organizational Silos:

Without DevOps/SRE, Development team will always focus on the implementation of the "new features" in the application however Operation team will always focus on the stability and reliability of the application.

With DevOps/SRE, it is a "Shared Ownership". Both Development team and Operations team will discuss and decide mutually on the product release and it's stability.

2. Accept failure as Normal:

Without DevOps/SRE, blaming each other.

With DevOps/SRE, here the priority is to restore the service, analyze the root cause and avoid the recurrence of the same issue. Hence it is Blameless Postmortems of issues.

3. Implement Gradual Change:

Without DevOps/SRE, development team releases any new feature with the product and that might cause any issue with the operations.

With DevOps/SRE, might follow "Canary Deployment" (and more) so that there wont be any high impact if any issue occurs.

4. Tooling and Automation:

Without DevOps/SRE, lot of repeated manual work

With DevOps/SRE, automate toil, avoid repeated manual tasks, use DevOps tools and engineering effect.

5. Measure Everything:

Without DevOps/SRE, no standard measurements,

With DevOps/SRE, user happiness is one of the key measurements, using three tools to do the measurement, SLI, SLO, SLA.

SLI or Service Level Indicator is a measurement the service provider uses for the goal (Eg: Uptime).

SLO or Service Level Objective is a goal that service provider wants to reach (Eg: 99.99 Uptime).

SLA or Service Level Agreement is a contract that the service provider promises customers on service availability, performance, etc (Uptime SLA is 99.99).