From 4bac7827b21aa0df025673399110477c39445bb4 Mon Sep 17 00:00:00 2001 From: Benny Nguyen Date: Mon, 22 Jan 2018 12:19:38 +0800 Subject: [PATCH] Refactor the list --- README.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/README.md b/README.md index 2e7188d..1dfd445 100644 --- a/README.md +++ b/README.md @@ -4,7 +4,7 @@ A curated list of selected readings to illustrate Scalability, Availability, and Stability Design Patterns in Back-end Development. #### What if your backend 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 as well as best pratices](#principles). +> 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 as well as best pratices](#principles). You can also check some [talks](#talks) of engineers from tech giants (Google, Facebook, Netflix, etc). #### What if your backend went down? > "Even if you lose all one day, you can build all over again if you retain your calm!" - Thuan Pham, CTO at Uber Technologies Inc. @@ -41,8 +41,8 @@ Contributions are always welcome! * [Avoid Overengineering](https://medium.com/@rdsubhas/10-modern-software-engineering-mistakes-bc67fbef4fc8) * [Design for Loose-coupling](https://dzone.com/articles/the-importance-of-loose-coupling-in-rest-api-desig) * [Design for Resiliency](http://highscalability.com/blog/2012/12/31/designing-for-resiliency-will-be-so-2013.html) -* [Design for Self-healing when failures occur](https://docs.microsoft.com/en-us/azure/architecture/guide/design-principles/self-healing) -* [Design for Scale out](https://docs.microsoft.com/en-us/azure/architecture/guide/design-principles/scale-out) +* [Design for Self-healing](https://docs.microsoft.com/en-us/azure/architecture/guide/design-principles/self-healing) +* [Design for Scaling Out](https://docs.microsoft.com/en-us/azure/architecture/guide/design-principles/scale-out) * [Best Practices for Scaling Out](https://blog.openshift.com/best-practices-for-horizontal-application-scaling/) * [Design for Evolution](https://docs.microsoft.com/en-us/azure/architecture/guide/design-principles/design-for-evolution) @@ -233,7 +233,7 @@ Contributions are always welcome! * [Scalability Rules: 50 Principles for Scaling Web Sites](http://scalabilityrules.com/) ## Talks -* [Harvard CS75 - Lecture 9: Scalability](https://www.youtube.com/watch?v=-W9F__D3oY4) +* [Building Real Time Infrastructure at Facebook](https://www.usenix.org/conference/srecon17americas/program/presentation/erlich) * [How We've Scaled Dropbox - Kevin Modzelewski, Back-end Engineer at Dropbox](https://www.youtube.com/watch?v=PE4gwstWhmc) * [Lessons of Scale at Facebook - Bobby Johnson, Director of Engineering at Facebook](https://www.youtube.com/watch?v=QCHiNEw73AU) * [Scaling Instagram Infrastructure - Lisa Guo, Instagram Engineering](https://www.youtube.com/watch?v=hnpzNAPiC0E)