mirror of
https://github.com/linkedin/school-of-sre
synced 2026-01-08 09:38:05 +00:00
Deployed df350bc with MkDocs version: 1.1.2
This commit is contained in:
Kalyanasundaram Somasundaram
@@ -214,6 +214,8 @@
|
||||
|
||||
<input class="md-nav__toggle md-toggle" data-md-toggle="toc" type="checkbox" id="__toc">
|
||||
|
||||
|
||||
|
||||
|
||||
<label class="md-nav__link md-nav__link--active" for="__toc">
|
||||
Github and Hooks
|
||||
@@ -228,6 +230,8 @@
|
||||
<nav class="md-nav md-nav--secondary" aria-label="Table of contents">
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
<label class="md-nav__title" for="__toc">
|
||||
<span class="md-nav__icon md-icon"></span>
|
||||
@@ -235,13 +239,6 @@
|
||||
</label>
|
||||
<ul class="md-nav__list" data-md-scrollfix>
|
||||
|
||||
<li class="md-nav__item">
|
||||
<a href="#git-with-github" class="md-nav__link">
|
||||
Git with Github
|
||||
</a>
|
||||
|
||||
</li>
|
||||
|
||||
<li class="md-nav__item">
|
||||
<a href="#hooks" class="md-nav__link">
|
||||
Hooks
|
||||
@@ -761,6 +758,8 @@
|
||||
<nav class="md-nav md-nav--secondary" aria-label="Table of contents">
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
<label class="md-nav__title" for="__toc">
|
||||
<span class="md-nav__icon md-icon"></span>
|
||||
@@ -768,13 +767,6 @@
|
||||
</label>
|
||||
<ul class="md-nav__list" data-md-scrollfix>
|
||||
|
||||
<li class="md-nav__item">
|
||||
<a href="#git-with-github" class="md-nav__link">
|
||||
Git with Github
|
||||
</a>
|
||||
|
||||
</li>
|
||||
|
||||
<li class="md-nav__item">
|
||||
<a href="#hooks" class="md-nav__link">
|
||||
Hooks
|
||||
@@ -802,9 +794,7 @@
|
||||
|
||||
|
||||
|
||||
<h1>Github and Hooks</h1>
|
||||
|
||||
<h2 id="git-with-github">Git with Github</h2>
|
||||
<h1 id="git-with-github">Git with Github</h1>
|
||||
<p>Till now all the operations we did were in our local repo while git also helps us in a collaborative environment. GitHub is one place on the internet where you can centrally host your git repos and collaborate with other developers.</p>
|
||||
<p>Most of the workflow will remain the same as we discussed, with addition of couple of things:</p>
|
||||
<ol>
|
||||
|
||||
@@ -733,7 +733,8 @@
|
||||
|
||||
|
||||
<h1 id="school-of-sre">School of SRE</h1>
|
||||
<p>Early 2019, we started visiting campuses to recruit the brightest minds to ensure LinkedIn and all the services that it is composed of is always available for everyone. This function at Linkedin falls in the purview of the Site Reliability Engineering team and Site Reliability Engineers ( SRE ) who are Software Engineers who specialize in reliability. SREs apply the principles of computer science and engineering to the design and development of computer systems: generally, large distributed ones. </p>
|
||||
<p><img alt="School of SRE" src="img/sos.png" />
|
||||
Early 2019, we started visiting campuses to recruit the brightest minds to ensure LinkedIn and all the services that it is composed of is always available for everyone. This function at Linkedin falls in the purview of the Site Reliability Engineering team and Site Reliability Engineers ( SRE ) who are Software Engineers who specialize in reliability. SREs apply the principles of computer science and engineering to the design and development of computer systems: generally, large distributed ones. </p>
|
||||
<p>As we continued on this journey we started getting a lot of questions from these campuses on what exactly site engineering roll entails? and, how could someone learn the skills and the disciplines involved to become a successful site engineer? Fast forward a few months, and a few of these campus students had joined LinkedIn either as Interns or as full time engineers to become a part of the Site Engineering team, we also had a few lateral hires who joined our organization who were not from a traditional SRE background. That's when a few of us got together and started to think about how we can on board new new graduate engineers to the site engineering team.</p>
|
||||
<p>There is a vast amount of resources scattered throughout the web on what are the roles and responsibilities of an SREs, how to monitor site health, handling incidents, maintain SLO/SLI etc. But there are very few resources out there guiding someone on what all basic skill sets one has to acquire as a beginner. Because of the lack of these resources we felt that individuals are having a tough time getting into open positions in the industry. We created School Of SRE as a starting point for anyone wanting to build their career in the role of SRE. </p>
|
||||
<p>In this course we are focusing on building strong foundational skills. The course is structured in a way to provide more real life examples and how learning each of the topics can play a bigger role in your day to day SRE life. Currently we are covering the following topics under the School Of SRE:</p>
|
||||
|
||||
BIN
sitemap.xml.gz
BIN
sitemap.xml.gz
Binary file not shown.
@@ -582,6 +582,8 @@
|
||||
|
||||
<input class="md-nav__toggle md-toggle" data-md-toggle="toc" type="checkbox" id="__toc">
|
||||
|
||||
|
||||
|
||||
|
||||
<label class="md-nav__link md-nav__link--active" for="__toc">
|
||||
Availability
|
||||
@@ -596,6 +598,8 @@
|
||||
<nav class="md-nav md-nav--secondary" aria-label="Table of contents">
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
<label class="md-nav__title" for="__toc">
|
||||
<span class="md-nav__icon md-icon"></span>
|
||||
@@ -604,23 +608,10 @@
|
||||
<ul class="md-nav__list" data-md-scrollfix>
|
||||
|
||||
<li class="md-nav__item">
|
||||
<a href="#ha-availability-common-nines" class="md-nav__link">
|
||||
HA - Availability - Common “Nines”
|
||||
</a>
|
||||
|
||||
<nav class="md-nav" aria-label="HA - Availability - Common “Nines”">
|
||||
<ul class="md-nav__list">
|
||||
|
||||
<li class="md-nav__item">
|
||||
<a href="#refer" class="md-nav__link">
|
||||
Refer
|
||||
</a>
|
||||
|
||||
</li>
|
||||
|
||||
</ul>
|
||||
</nav>
|
||||
|
||||
</li>
|
||||
|
||||
<li class="md-nav__item">
|
||||
@@ -839,6 +830,8 @@
|
||||
<nav class="md-nav md-nav--secondary" aria-label="Table of contents">
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
<label class="md-nav__title" for="__toc">
|
||||
<span class="md-nav__icon md-icon"></span>
|
||||
@@ -847,23 +840,10 @@
|
||||
<ul class="md-nav__list" data-md-scrollfix>
|
||||
|
||||
<li class="md-nav__item">
|
||||
<a href="#ha-availability-common-nines" class="md-nav__link">
|
||||
HA - Availability - Common “Nines”
|
||||
</a>
|
||||
|
||||
<nav class="md-nav" aria-label="HA - Availability - Common “Nines”">
|
||||
<ul class="md-nav__list">
|
||||
|
||||
<li class="md-nav__item">
|
||||
<a href="#refer" class="md-nav__link">
|
||||
Refer
|
||||
</a>
|
||||
|
||||
</li>
|
||||
|
||||
</ul>
|
||||
</nav>
|
||||
|
||||
</li>
|
||||
|
||||
<li class="md-nav__item">
|
||||
@@ -960,9 +940,7 @@
|
||||
|
||||
|
||||
|
||||
<h1>Availability</h1>
|
||||
|
||||
<h2 id="ha-availability-common-nines">HA - Availability - Common “Nines”</h2>
|
||||
<h1 id="ha-availability-common-nines">HA - Availability - Common “Nines”</h1>
|
||||
<p>Availability is generally expressed as “Nines”, common ‘Nines’ are listed below.</p>
|
||||
<table>
|
||||
<thead>
|
||||
|
||||
@@ -606,38 +606,13 @@
|
||||
|
||||
<input class="md-nav__toggle md-toggle" data-md-toggle="toc" type="checkbox" id="__toc">
|
||||
|
||||
|
||||
|
||||
<label class="md-nav__link md-nav__link--active" for="__toc">
|
||||
Conclusion
|
||||
<span class="md-nav__icon md-icon"></span>
|
||||
</label>
|
||||
|
||||
<a href="./" class="md-nav__link md-nav__link--active">
|
||||
Conclusion
|
||||
</a>
|
||||
|
||||
|
||||
<nav class="md-nav md-nav--secondary" aria-label="Table of contents">
|
||||
|
||||
|
||||
|
||||
<label class="md-nav__title" for="__toc">
|
||||
<span class="md-nav__icon md-icon"></span>
|
||||
Table of contents
|
||||
</label>
|
||||
<ul class="md-nav__list" data-md-scrollfix>
|
||||
|
||||
<li class="md-nav__item">
|
||||
<a href="#conclusion" class="md-nav__link">
|
||||
Conclusion
|
||||
</a>
|
||||
|
||||
</li>
|
||||
|
||||
</ul>
|
||||
|
||||
</nav>
|
||||
|
||||
</li>
|
||||
|
||||
|
||||
@@ -745,21 +720,8 @@
|
||||
<nav class="md-nav md-nav--secondary" aria-label="Table of contents">
|
||||
|
||||
|
||||
|
||||
|
||||
<label class="md-nav__title" for="__toc">
|
||||
<span class="md-nav__icon md-icon"></span>
|
||||
Table of contents
|
||||
</label>
|
||||
<ul class="md-nav__list" data-md-scrollfix>
|
||||
|
||||
<li class="md-nav__item">
|
||||
<a href="#conclusion" class="md-nav__link">
|
||||
Conclusion
|
||||
</a>
|
||||
|
||||
</li>
|
||||
|
||||
</ul>
|
||||
|
||||
</nav>
|
||||
</div>
|
||||
@@ -772,9 +734,7 @@
|
||||
|
||||
|
||||
|
||||
<h1>Conclusion</h1>
|
||||
|
||||
<h2 id="conclusion">Conclusion</h2>
|
||||
<h1 id="conclusion">Conclusion</h1>
|
||||
<p>Armed with these principles, we hope the course will give a fresh perspective to design software systems. It might be over engineering to get all this on day zero. But some are really important from day 0 like eliminating single points of failure, making scalable services by just increasing replicas. As a bottleneck is reached, we can split code by services, shard data to scale. As the organisation matures, bringing in <a href="https://en.wikipedia.org/wiki/Chaos_engineering">chaos engineering</a> to measure how systems react to failure will help in designing robust software systems.</p>
|
||||
|
||||
|
||||
|
||||
@@ -594,6 +594,8 @@
|
||||
|
||||
<input class="md-nav__toggle md-toggle" data-md-toggle="toc" type="checkbox" id="__toc">
|
||||
|
||||
|
||||
|
||||
|
||||
<label class="md-nav__link md-nav__link--active" for="__toc">
|
||||
Fault Tolerance
|
||||
@@ -608,6 +610,8 @@
|
||||
<nav class="md-nav md-nav--secondary" aria-label="Table of contents">
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
<label class="md-nav__title" for="__toc">
|
||||
<span class="md-nav__icon md-icon"></span>
|
||||
@@ -616,14 +620,6 @@
|
||||
<ul class="md-nav__list" data-md-scrollfix>
|
||||
|
||||
<li class="md-nav__item">
|
||||
<a href="#fault-tolerance" class="md-nav__link">
|
||||
Fault Tolerance
|
||||
</a>
|
||||
|
||||
<nav class="md-nav" aria-label="Fault Tolerance">
|
||||
<ul class="md-nav__list">
|
||||
|
||||
<li class="md-nav__item">
|
||||
<a href="#fault-tolerance-failure-metrics" class="md-nav__link">
|
||||
Fault Tolerance - Failure Metrics
|
||||
</a>
|
||||
@@ -642,22 +638,22 @@
|
||||
</nav>
|
||||
|
||||
</li>
|
||||
|
||||
<li class="md-nav__item">
|
||||
|
||||
<li class="md-nav__item">
|
||||
<a href="#fault-tolerance-fault-isolation-terms" class="md-nav__link">
|
||||
Fault Tolerance - Fault Isolation Terms
|
||||
</a>
|
||||
|
||||
</li>
|
||||
|
||||
<li class="md-nav__item">
|
||||
|
||||
<li class="md-nav__item">
|
||||
<a href="#swimlane-principles" class="md-nav__link">
|
||||
Swimlane Principles
|
||||
</a>
|
||||
|
||||
</li>
|
||||
|
||||
<li class="md-nav__item">
|
||||
|
||||
<li class="md-nav__item">
|
||||
<a href="#swimlane-approaches" class="md-nav__link">
|
||||
Swimlane Approaches
|
||||
</a>
|
||||
@@ -676,17 +672,12 @@
|
||||
</nav>
|
||||
|
||||
</li>
|
||||
|
||||
<li class="md-nav__item">
|
||||
|
||||
<li class="md-nav__item">
|
||||
<a href="#sre-use-cases" class="md-nav__link">
|
||||
SRE Use cases:
|
||||
</a>
|
||||
|
||||
</li>
|
||||
|
||||
</ul>
|
||||
</nav>
|
||||
|
||||
</li>
|
||||
|
||||
</ul>
|
||||
@@ -812,6 +803,8 @@
|
||||
<nav class="md-nav md-nav--secondary" aria-label="Table of contents">
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
<label class="md-nav__title" for="__toc">
|
||||
<span class="md-nav__icon md-icon"></span>
|
||||
@@ -820,14 +813,6 @@
|
||||
<ul class="md-nav__list" data-md-scrollfix>
|
||||
|
||||
<li class="md-nav__item">
|
||||
<a href="#fault-tolerance" class="md-nav__link">
|
||||
Fault Tolerance
|
||||
</a>
|
||||
|
||||
<nav class="md-nav" aria-label="Fault Tolerance">
|
||||
<ul class="md-nav__list">
|
||||
|
||||
<li class="md-nav__item">
|
||||
<a href="#fault-tolerance-failure-metrics" class="md-nav__link">
|
||||
Fault Tolerance - Failure Metrics
|
||||
</a>
|
||||
@@ -846,22 +831,22 @@
|
||||
</nav>
|
||||
|
||||
</li>
|
||||
|
||||
<li class="md-nav__item">
|
||||
|
||||
<li class="md-nav__item">
|
||||
<a href="#fault-tolerance-fault-isolation-terms" class="md-nav__link">
|
||||
Fault Tolerance - Fault Isolation Terms
|
||||
</a>
|
||||
|
||||
</li>
|
||||
|
||||
<li class="md-nav__item">
|
||||
|
||||
<li class="md-nav__item">
|
||||
<a href="#swimlane-principles" class="md-nav__link">
|
||||
Swimlane Principles
|
||||
</a>
|
||||
|
||||
</li>
|
||||
|
||||
<li class="md-nav__item">
|
||||
|
||||
<li class="md-nav__item">
|
||||
<a href="#swimlane-approaches" class="md-nav__link">
|
||||
Swimlane Approaches
|
||||
</a>
|
||||
@@ -880,17 +865,12 @@
|
||||
</nav>
|
||||
|
||||
</li>
|
||||
|
||||
<li class="md-nav__item">
|
||||
|
||||
<li class="md-nav__item">
|
||||
<a href="#sre-use-cases" class="md-nav__link">
|
||||
SRE Use cases:
|
||||
</a>
|
||||
|
||||
</li>
|
||||
|
||||
</ul>
|
||||
</nav>
|
||||
|
||||
</li>
|
||||
|
||||
</ul>
|
||||
@@ -906,9 +886,7 @@
|
||||
|
||||
|
||||
|
||||
<h1>Fault Tolerance</h1>
|
||||
|
||||
<h2 id="fault-tolerance">Fault Tolerance</h2>
|
||||
<h1 id="fault-tolerance">Fault Tolerance</h1>
|
||||
<p>Failures are not avoidable in any system and will happen all the time, hence we need to build systems that can tolerate failures or recover from them.</p>
|
||||
<ul>
|
||||
<li>In systems, failure is the norm rather than the exception.</li>
|
||||
|
||||
Reference in New Issue
Block a user