From 21a6f28acb2d57c71a5cec7291a696b4764fdaf0 Mon Sep 17 00:00:00 2001 From: Benny Nguyen Date: Sat, 20 Jan 2018 22:14:49 +0800 Subject: [PATCH] Understand why Cache is King! --- README.md | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/README.md b/README.md index c7e73b4..a807cf2 100644 --- a/README.md +++ b/README.md @@ -26,20 +26,20 @@ Contributions are always welcome! ## Principles * [CAP Theorem and Trade-offs](http://robertgreiner.com/2014/08/cap-theorem-revisited/) * [Scaling Up and Scaling Out](https://blogs.technet.microsoft.com/admoore/2015/02/17/scaling-out-vs-scaling-up/) -* [Best Practices for Scaling Out](https://blog.openshift.com/best-practices-for-horizontal-application-scaling/) -* [Understanding Latency](http://highscalability.com/latency-everywhere-and-it-costs-you-sales-how-crush-it) -* [Maximal Throughput with Acceptable Latency (Dropbox case)](https://blogs.dropbox.com/tech/2017/09/optimizing-web-servers-for-high-throughput-and-low-latency/) * [ACID and BASE](https://neo4j.com/blog/acid-vs-base-consistency-models-explained/) * [Synchronous and Asynchronous](https://blogs.msdn.microsoft.com/csliu/2009/08/04/inside-scalable-io-model-in-sync-async-way/) +* [SQL and NoSQL](https://www.upwork.com/hiring/data/sql-vs-nosql-databases-whats-the-difference/) +* [Understand why Cache is King!](https://www.stevesouders.com/blog/2012/10/11/cache-is-king/) +* [Understand Latency](http://highscalability.com/latency-everywhere-and-it-costs-you-sales-how-crush-it) * [Architecture Issues When Scaling Web Applications: Bottlenecks, Database, CPU, IO](http://highscalability.com/blog/2014/5/12/4-architecture-issues-when-scaling-web-applications-bottlene.html) -* [Performance and Scalability patterns](https://docs.microsoft.com/en-us/azure/architecture/patterns/category/performance-scalability) * [Advantages and Drawbacks of Microservices](https://cloudacademy.com/blog/microservices-architecture-challenge-advantage-drawback/) * [Avoid Overengineering](https://medium.com/@rdsubhas/10-modern-software-engineering-mistakes-bc67fbef4fc8) * [Don't Repeat Yourself (DRY)](https://softwareengineering.stackexchange.com/questions/103233/why-is-dry-important) * [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 Scale out](https://docs.microsoft.com/en-us/azure/architecture/guide/design-principles/scale-out) +* [Best Practices for Scaling Out (by Steve Souders, author of "High Performance Web Sites")](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) ## Scalability