mirrors
/
system-design-primer
mirror of https://github.com/donnemartin/system-design-primer.git
1
0
Fork 0
Code Issues Projects Releases Wiki Activity

Update README.md

pull/237/head
Donne Martin 2019-05-12 07:16:51 -04:00 committed by GitHub
parent eee63ed1e1
commit 2567f1cb43
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
README.md
View File

@ -530,7 +530,7 @@ This topic is further discussed in the [Database](#database) section:
### Availability in numbers
Availability is generally quantified by uptime (or downtime) as a percentage of time the service is available. Availability is often measured in number of 9s--a service with 99.99% availability is described as having four 9s.
Availability is often quantified by uptime (or downtime) as a percentage of time the service is available. Availability is generally measured in number of 9s--a service with 99.99% availability is described as having four 9s.
#### 99.9% availability - three 9s
@ -554,7 +554,7 @@ Availability is generally quantified by uptime (or downtime) as a percentage of
If a service consists of multiple components prone to failure, the service's overall availability depends on whether the components are in sequence or in parallel.
###### In Sequence
###### In sequence
Overall availability decreases when two components with availability < 100% are in sequence:
@ -564,7 +564,7 @@ Availability (Total) = Availability (Foo) * Availability (Bar)
If both `Foo` and `Bar` each had 99.9% availability, their total availability in sequence would be 99.8%.
###### In Parallel
###### In parallel
Overall availability increases when two components with availability < 100% are in parallel: