Skip to content

Add clarity to availability pattern description #314

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
wants to merge 1 commit into from
Closed

Add clarity to availability pattern description #314

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 4 additions & 1 deletion README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -494,7 +494,10 @@ This approach is seen in file systems and RDBMSes. Strong consistency works wel

## Availability patterns

There are two main patterns to support high availability: **fail-over** and **replication**.
There are two main patterns to support high availability: **fail-over** and **replication**. These patterns are not competing, but complementing each other. To achieve availability, one needs both fail-over and replication.

Fail-over
Active-passive

### Fail-over

Expand Down