From 1f92667ccc5e4ad80fc0b82f8034bd945c27ec54 Mon Sep 17 00:00:00 2001 From: binhnguyennus Date: Sun, 8 Apr 2018 23:39:31 +0800 Subject: [PATCH] Keep three lines for each Introduction sub-section --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 20c23ed..741b894 100644 --- a/README.md +++ b/README.md @@ -1,6 +1,6 @@ # High Scalability, High Availability, High Stability, High Performance, and High Intelligence Back-end Designs -An updated and curated list of selected readings to illustrate High Scalability, High Availability, High Stability, High Performance, and High Intelligence Back-end Designs. Concepts are explained in the articles of notable engineers (Werner Vogels, James Hamilton, Martin Kleppmann, etc) and credible references (highscalability.com, infoq.com, official engineering blogs). 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, High Stability, High Performance, and High Intelligence Back-end Designs. Concepts are explained in the articles of notable engineers (Jeff Dean, Werner Vogels, James Hamilton, etc) and credible references. Case studies are taken from battle-tested systems those are serving millions to billions of users. #### 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.