en 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 Google puts it, the ultimate aim for SREs is to "automate their way out of a job. Doing so eliminates work in progress for both stakeholders, encourages developers to concentrate solely on the creation of functionality, and allows them to concentrate on automating the next mission.
SREs work closely with product developers to ensure those non-functional criteria such as availability, functionality, protection, and maintainability are met by the developed solution. To ensure that the software delivery pipes effective as possible, they also collaborate with release engineers.
The key standards of the Site Reliability Engineering
Signup today to claim your Discount. Get Started before it's too late!
