GitHub/school-of-sre
1
0
Fork 0
mirror of https://github.com/linkedin/school-of-sre synced 2026-01-20 23:48:03 +00:00
Code Issues Packages Projects Releases Wiki Activity

Fixing links and standardising titles

Browse Source
This commit is contained in:
Kalyanasundaram Somasundaram
2020-11-23 20:16:23 +05:30
parent bf2c85d6b0
commit da2599ebe5
19 changed files with 63 additions and 73 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
courses/systems_design/availability.md
View File

@@ -76,7 +76,7 @@ The combined availability of the system is
**KEY TAKEAWAYS:** Strive for active/active rather than active/passive solutions, they have a lesser risk of cross over being unreliable. Use LB and right load balancing methods to ensure reliable failover. Model and build your data systems to ensure data is correctly handled when crossover happens. Generally DB systems follow active/passive semantics for writes. Masters accept writes and when master goes down, follower is promoted to master(active from being passive) to accept writes. We have to be careful here that the cutover never introduces more than one masters. This problem is called a split brain.
## SRE Use cases
## Applications in SRE role
1. SRE works on deciding an acceptable SLA and make sure system is available to achieve the SLA
2. SRE is involved in architecture design right from building the data center to make sure site is not affected by network switch, hardware, power or software failures
3. SRE also run mock drills of failures to see how the system behaves in uncharted territory and comes up with a plan to improve availability if there are misses.