From 2ba706bc3295f39ef66f8afe42f3d2029245aa11 Mon Sep 17 00:00:00 2001 From: binhnguyennus Date: Sun, 4 Mar 2018 11:01:15 +0800 Subject: [PATCH] Refactor --- README.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/README.md b/README.md index 133e75f..9a78bf6 100644 --- a/README.md +++ b/README.md @@ -1,6 +1,6 @@ -# Awesome Scalability, Availability, and Stability Back-end Design Patterns +# High Scalability, High Availability, and High Stability Design Patterns in Back-end Systems -An updated and curated list of selected readings to illustrate Scalability, Availability, and Stability Design Patterns in Back-end Development. Concepts are explained in the articles of notable engineers (Werner Vogels, James Hamilton, Jeff Atwood, Martin Fowler, Robert C. Martin, Tom White, Martin Kleppmann) and high quality reference sources (highscalability.com, infoq.com, official engineering blogs, etc). Case studies are taken from battle-tested systems those are serving millions to billions of users (Netflix, Alibaba, Flipkart, LINE, Spotify, etc). +An updated and curated list of selected readings to illustrate High Scalability, High Availability, and High Stability Design Patterns in Back-end. Concepts are explained in the articles of notable engineers (Werner Vogels, James Hamilton, Jeff Atwood, Martin Fowler, Robert C. Martin, Tom White, Martin Kleppmann) and high quality reference sources (highscalability.com, infoq.com, official engineering blogs, etc). Case studies are taken from battle-tested systems those are serving millions to billions of users (Netflix, Alibaba, Flipkart, LINE, Spotify, etc). #### What if your Back-end went slow? > Understand your problems: performance problem (slow for a single user) or scalability problem (fast for a single user but slow under heavy load) by reviewing [design principles](#principles). You can also check some [talks](#talks) of elite engineers from tech giants (Google, Facebook, Instagram, etc) to see how they build and scale their systems.