Why two names?

DevOps vs Site Reliability Engineering (SRE)


Application development process is currently containing limits which remediate action has been lacking and infrastructure may easily break down. While DevOps automation is only focusing on development and deployment, problems often occur, and developers face challenges frequently. IT operations at first do not cope with automation, and all coding are written manually. Around 10 years ago, automation become emphasized, developers and operation teams continuously building up agile software application.In fact, IT operational management is not mature enough which causes instable application and minor defects occur frequently.


Software emphasizing in IT operation

An operation team will always include SRE which engineers emphasise on implementing software to automate IT operations andpreempt failures. Testing codes execution will between developmentand operations while it requires an advance technology in dealing with infrastructural and remedial issues. The software approach merges with IT operations which build up nimbleness between application and infrastructure.


DevOps vs SRE

For monitoring and remediation, DevOps deals with situation before failure occur, it secures the condition will not be severe whichbreak down the entire system. While for SRE, it deals with situation after failure occur. It analyses the root of the problem after failure has been made and its objective is to minimize defects occurrence in the long run.

In the software lifecycle development, DevOps is focusing on effectively delivering software application and identify any possible problems and act as the role of taking precautions within infrastructure and application. On the other hand, SRE is focusing onthe management towards application deployment and secure the reliability of application within the environment for production.

Considering the speed and cost of the increasing change, DevOps is relating to releasing new updates or some new features developed, focusing on minimizing the product life cycle and continuous development and synthesisation, while it is insignificant and hard to measure the cost of all this. But for SRE, it is about adapting and consolidating newly introduced updates and features. It accepts minimal defects occur in the whole process which is as expected. This is a way to accept changes and remediation with agility and prevent rigid and not knowing what to do when facing failures. Accepting a certain amount of failure with efficient testing and remediation may significantly reduce the cost suffer by enterprises once actual failure occurs.