Site Reliability Engineering (SRE) Handbook
How SRE implements DevOps
カートのアイテムが多すぎます
カートに追加できませんでした。
ウィッシュリストに追加できませんでした。
ほしい物リストの削除に失敗しました。
ポッドキャストのフォローに失敗しました
ポッドキャストのフォロー解除に失敗しました
聴き放題対象外タイトルです。Audible会員登録で、非会員価格の30％OFFで購入できます。
Site Reliability Engineering (SRE) Handbook
-
ナレーター：
-
Austin R Stoler
-
著者：
-
Stephen Fleming
このコンテンツについて
Well, you have been hearing a lot about DevOps lately. Wait until you meet a Site Reliability Engineer (SRE)!
Google is the pioneer in the SRE movement, and Ben Treynor from Google defines SRE as, “what happens when a software engineer is tasked with what used to be called operations”. The ongoing struggles between development and ops team for software releases have been sorted out by mathematical formula for green or red-light launches!
Sounds interesting. Now, do you know which the organizations are using SRE? Apart from Google, you can find SRE job postings from LinkedIn, Twitter, Uber, Oracle, Twitter, and many more.
I also enquired about the average salary of a SRE in USA, and all the leading sites gave similar results: around $130,000 per year. Also, currently, the most-sought job titles in tech domain are DevOps and Site Reliability Engineer.
So, do you want to know how SRE works, what the required skill sets are, how a software engineer can transit to SRE role, how LinkedIn used SRE to facilitate the deployment process?
Here is your chance to dive into the SRE role and know what it takes to be and implement best SRE practices.
The DevOps, Continuous Delivery, and SRE movements are here to stay and grow. It's time you to ride the wave!
So, don’t wait! Take action!
©2018 Stephen Fleming (P)2018 Stephen Fleming