This makes the introduction of automation essential. In order to bring together reliability and speed, SREs must eliminate as much manual work as possible so that they can focus on the actual engineering. Learn more about SRE and the differences and similarities between SRE and DevOps here. In short terms, the aim of an SRE is to push development forward to improve systems quickly, while ensuring high quality, reliable and flexible production environments and applications.
The concept is not vastly different from DevOps, as its core focus is to bring the, sometimes contradicting, aims of Development and Operations together. SRE, or Site Reliability Engineering, is a term coined by Google to describe a set of practices and a culture, as well as a job role (Site Reliability Engineer). Make sure you watch our on-demand webinar with Credit Suisse, where Credit Suisse’s VP of SRE shares the strategies the organization employed to reduce toil with test automation, boost efficiency and enable operational teams to focus on more satisfying, high-value work. In this blog post, we’ll dive into the role toil plays is SRE and what operational teams can do to reduce the time spent on toil. For Site Reliability Engineering (SRE) teams, the aim is to reduce or even eliminate toil in order to maximize the time spent on engineering and innovation. Toil is a term coined by Google to describe tedious, repetitive tasks associated with running a production environment.
0 kommentar(er)
