{"id":52646,"date":"2018-06-21T15:17:19","date_gmt":"2018-06-21T14:17:19","guid":{"rendered":"http:\/\/content.n4stack.io\/?page_id=52646"},"modified":"2018-09-19T11:53:18","modified_gmt":"2018-09-19T10:53:18","slug":"what-sre","status":"publish","type":"page","link":"http:\/\/content.n4stack.io\/what-sre\/","title":{"rendered":"What is SRE?"},"content":{"rendered":"<p>[et_pb_section bb_built=&#8221;1&#8243; _builder_version=&#8221;3.0.47&#8243;][et_pb_row][et_pb_column type=&#8221;3_4&#8243;][et_pb_text _builder_version=&#8221;3.7.1&#8243; header_font_size=&#8221;44px&#8221;]<\/p>\n<h1><strong>WHAT IS SRE?<\/strong><\/h1>\n<p>[\/et_pb_text][et_pb_text _builder_version=&#8221;3.7.1&#8243;]<\/p>\n<p><em>What is SRE?<\/em> Site Reliability Engineering (SRE) is an operational model created by Google in 2003 which uses software engineering principles to efficiently manage complex infrastructure.<\/p>\n<p>The role of a Site Reliability Engineer is becoming increasingly popular with adoption of the model. Broadly speaking an engineering team will have a blend of skills including sysadmin, security, automation and importantly the ability to code. The target of the role is to spend half of the time on projects to improve reliability with a heavy use of automation and the other providing operational support. Closely aligned with a DevOps culture the SRE team are empowered to drive proactive improvement, embracing automation and new architecture models. This 50% of time focused on improvement provides the efficiencies to reduce the operational support burden, maintaining an efficient balance.<\/p>\n<p>The following areas are core principles of a Site Reliability Engineering practice:<\/p>\n<ul>\n<li>Agreeing an error budget (outage % SLA) with the development team<\/li>\n<li>Having stringent acceptance testing before having to supporting an application<\/li>\n<li>Obsessive use of automation<\/li>\n<li>Site Reliability Engineers who can code<\/li>\n<li>Spend 50% time of tickets &amp; 50% on (improvement) project work<\/li>\n<\/ul>\n<p>Many well known companies use a Site Reliability Engineering operational approach including Uber, Netflix, Atlassian, Amazon, Facebook &amp; Twitter.<\/p>\n<p>[\/et_pb_text][\/et_pb_column][et_pb_column type=&#8221;1_4&#8243;][et_pb_testimonial author=&#8221;Ben Treynor&#8221; job_title=&#8221;Founder of Google\u2019s SRE Team&#8221; quote_icon_color=&#8221;#e05206&#8243; quote_icon_background_color=&#8221;#ffffff&#8221; _builder_version=&#8221;3.7.1&#8243; body_text_color=&#8221;#ffffff&#8221; body_font_size=&#8221;20&#8243; background_color=&#8221;#e05206&#8243; background_image=&#8221;http:\/\/content.n4stack.io\/wp-content\/uploads\/2018\/06\/Data_Background.jpg&#8221; border_color_all=&#8221;#595959&#8243; border_color_all_portrait=&#8221;#595959&#8243; text_orientation=&#8221;center&#8221; background_layout=&#8221;dark&#8221; custom_margin=&#8221;50px|||&#8221;]<\/p>\n<p>SRE is \u201cwhat happens when a software engineer is tasked with what used to be called operations.\u201d<\/p>\n<p>[\/et_pb_testimonial][et_pb_image _builder_version=&#8221;3.7.1&#8243; src=&#8221;http:\/\/content.n4stack.io\/wp-content\/uploads\/2018\/06\/SRE-Book.png&#8221; url=&#8221;https:\/\/landing.google.com\/sre\/book\/index.html&#8221; url_new_window=&#8221;on&#8221; align=&#8221;center&#8221; show_bottom_space=&#8221;off&#8221; \/][\/et_pb_column][\/et_pb_row][\/et_pb_section]<\/p>\n","protected":false},"excerpt":{"rendered":"<p>WHAT IS SRE? What is SRE? Site Reliability Engineering (SRE) is an operational model created by Google in 2003 which uses software engineering principles to efficiently manage complex infrastructure. The role of a Site Reliability Engineer is becoming increasingly popular with adoption of the model. Broadly speaking an engineering team will have a blend of [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":52714,"parent":0,"menu_order":0,"comment_status":"closed","ping_status":"closed","template":"","meta":{"_et_pb_use_builder":"on","_et_pb_old_content":"","_et_gb_content_width":""},"yst_prominent_words":[1790,14,1792,1781,1794,582,581,70,1789,1785,1784,111,1146,1783,1782,468,1780,1791,19,97],"_links":{"self":[{"href":"http:\/\/content.n4stack.io\/wp-json\/wp\/v2\/pages\/52646"}],"collection":[{"href":"http:\/\/content.n4stack.io\/wp-json\/wp\/v2\/pages"}],"about":[{"href":"http:\/\/content.n4stack.io\/wp-json\/wp\/v2\/types\/page"}],"author":[{"embeddable":true,"href":"http:\/\/content.n4stack.io\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"http:\/\/content.n4stack.io\/wp-json\/wp\/v2\/comments?post=52646"}],"version-history":[{"count":23,"href":"http:\/\/content.n4stack.io\/wp-json\/wp\/v2\/pages\/52646\/revisions"}],"predecessor-version":[{"id":54074,"href":"http:\/\/content.n4stack.io\/wp-json\/wp\/v2\/pages\/52646\/revisions\/54074"}],"wp:featuredmedia":[{"embeddable":true,"href":"http:\/\/content.n4stack.io\/wp-json\/wp\/v2\/media\/52714"}],"wp:attachment":[{"href":"http:\/\/content.n4stack.io\/wp-json\/wp\/v2\/media?parent=52646"}],"wp:term":[{"taxonomy":"yst_prominent_words","embeddable":true,"href":"http:\/\/content.n4stack.io\/wp-json\/wp\/v2\/yst_prominent_words?post=52646"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}