Availability patterns description

[njacharya]

A description is incomplete. It should mention:

These patterns are not competing, but complementing each other. To achieve availability, one needs both fail-over and replication.

right after

"There are two main patterns to support high availability: fail-over and replication. "

[acbnelsalvador]

Gracias por los que comenten pero soy nuevo en esto y estoy en prueba y error aprendiendo.

[donnemartin]

Hi @njacharya good catch. Anyone want to submit a pull request? I think changing this:

There are two main patterns to support high availability: fail-over and replication.

To this:

There are two complementary patterns to support high availability: fail-over and replication.

Would bring more clarity.

[njacharya]

#439 From: Donne Martin <notifications@github.com> Date: Saturday, July 4, 2020 at 09:13 To: donnemartin/system-design-primer <system-design-primer@noreply.github.com> Cc: Nachiket Acharya <Nachiket.Acharya@microsoft.com>, Mention <mention@noreply.github.com> Subject: Re: [donnemartin/system-design-primer] Availability patterns description (#313) Hi @njacharya<https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnjacharya&data=02%7C01%7CNachiket.Acharya%40microsoft.com%7Cd925ed67b2554cf339ac08d820353def%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637294760343732656&sdata=tIa3PG4aTsW83osiZ3dXG5IG2qEtlnKjYebHsfZnOiY%3D&reserved=0> good catch. Anyone want to submit a pull request? I think changing this: There are two main patterns to support high availability: fail-over and replication. To this: There are two complementary patterns to support high availability: fail-over and replication. Would bring more clarity. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub<https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fdonnemartin%2Fsystem-design-primer%2Fissues%2F313%23issuecomment-653784421&data=02%7C01%7CNachiket.Acharya%40microsoft.com%7Cd925ed67b2554cf339ac08d820353def%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637294760343742653&sdata=1HQ4MW8UAz96XUlHc52zm3Uz80IoRElb%2BGGyBOwl7nw%3D&reserved=0>, or unsubscribe<https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAL7EX5WKNNEVDCPQIFHJVLTRZ5IL7ANCNFSM4IMMAEMA&data=02%7C01%7CNachiket.Acharya%40microsoft.com%7Cd925ed67b2554cf339ac08d820353def%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637294760343742653&sdata=Kue2A%2BUh8eyErmXJXnGrNRSnIWxMydM0CxhZFbttuvU%3D&reserved=0>.

[nacharya-msft]

Hi @njacharya good catch. Anyone want to submit a pull request? I think changing this:

There are two main patterns to support high availability: fail-over and replication.

To this:

There are two complementary patterns to support high availability: fail-over and replication.

Would bring more clarity.

created new pull request: #439