SRE

Site Reliability Engineering

Over the years the name of the title for Site Reliability Engineer has been changed.
Initially, it was called Middleware team, then Devops/Webops team, and now as Site Reliability Team.

Per the definition of Microsoft
“Middleware is software which lies between an operating system and the applications running on it. Common middleware examples include database middleware, application server middleware, message-oriented middleware, web middleware, and transaction-processing monitors.”
When it comes to a human who is working on this middleware system is essentially a middleware engineer who maintain the software systems between Hardware and Software.
The middleware team was transitioned to Devops/Webops team.

Devops stands for development and operations. Additional to Middleware activities, the devops engineer has a strong focus on continuous integration and continuous delivery.
Per wiki “CI/CD bridges the gaps between development and operation activities and teams by enforcing automation in building, testing, and deployment of applications. Modern-day DevOps practices involve continuous development, continuous testing, continuous integration, continuous deployment, and continuous monitoring of software applications throughout their development life cycle. The CI/CD practice or CI/CD pipeline forms the backbone of modern-day DevOps operations
In software engineering, CI/CD or CICD generally refers to the combined practices of continuous integration and either continuous delivery or continuous deployment. CI/CD bridges the gaps between development and operation activities and teams by enforcing automation in building, testing, and deployment of applications.”
Developing systems that can market the project to a live website (or production) at the earliest is a key emphasis on devops.

Devops is transitioned to SRE, which stands for site reliability engineer.
Maintaining the website without any downtime, recover the website if there is an issue occurs, conduct preventive measures for foreseeing problems, fix possible security issues are some of the important tasks performed by the Site Reliability team.
Per redhat,
“SRE takes the tasks that have historically been done by operations teams, often manually, and instead gives them to engineers or ops teams who use software and automation to solve problems and manage production systems.
SRE is a valuable practice when creating scalable and highly reliable software systems. It helps you manage large systems through code, which is more scalable and sustainable for sysadmins managing thousands or hundreds of thousands of machines.
The concept of site reliability engineering comes from the Google engineering team and is credited to Ben Treynor Sloss.
SRE helps teams find a balance between releasing new features and making sure that they are reliable for users.”