Site reliability engineering is a process of using engineering tactics in operations automation. Some examples of this are change management, response to incidence, emergency tasks, and general system management. These tasks are sometimes performed manually by teams, but SRE makes these processes simpler and faster.
What is the ultimate goal of SRE? DevOps and SRE go hand in hand. SRE is just more explicit in its objectives. SRE’s goal is to equalize the need to rapidly develop and the need to achieve performance metrics in a project’s scope. Ultimately it’s a way to balance milestones and rate of development without affecting the life cycle of a project and manages expectations for the end-user. Learn more about DevOps culture here
What do SRE experts do? SRE admins and SRE engineers find the risk involved in development (error budgeting), and automate based on that level of risk to mitigate issues.
On a DevOps team, people involved in SRE are the liaison between the developers and operations. They provide important data and metrics that allow for changes to be made rapidly and new components to be built correctly according to a service level agreement.