In 2003, before the DevOps revolution, Site Reliability Engineering (SRE) was born at Google when the first team of software engineers was tasked with making Google's already large-scale sites more stable, efficient, and scalable. The practices they built reacted so well to the needs of Google that they were also embraced by other major tech businesses, such as Amazon and Netflix, and introduced new practices to the table.
What is Site reliability engineering?
Site reliability engineering (SRE) is an approach to IT operations in software engineering. SRE teams use the software as a tool to handle processes, repair issues, and automate tasks for operations. SRE takes on the tasks that operations teams have historically done, often manually, and instead gives them to engineers or operations teams that use software and automation to solve problems and manage production systems.
When developing scalable and highly stable software systems, SRE is a valuable activity. It allows you to manage massive systems through code, which is more flexible and sustainable for thousands or hundreds of thousands of machines to be operated by sysadmins. Ben Treynor Sloss is credited with the idea of site reliability engineering coming from the Google engineering team.
What does a site reliability engineer do?
They divide their time between operations/on-call responsibilities and systems and software creation that help improve the efficiency and performance of the web. Google places a great deal of focus on SREs not spending more than 50 percent of their time on tasks and finds a sign of system ill-health any breach of this law.
As Goo
Signup today to claim your Discount. Get Started before it's too late!
