From 6f0fbff5f23c3300dee50bf9464d378c72764bf6 Mon Sep 17 00:00:00 2001 From: Benny Nguyen Date: Wed, 24 Jan 2018 21:17:50 +0800 Subject: [PATCH] =?UTF-8?q?(UI)=20Design=20Doesn=E2=80=99t=20Scale=20-=20S?= =?UTF-8?q?tanley=20Wood,=20Design=20Director=20at=20Spotify?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit --- README.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/README.md b/README.md index 2f04e91..8e5c455 100644 --- a/README.md +++ b/README.md @@ -32,7 +32,7 @@ Contributions are always welcome! * [Blocking/Non-Blocking and Sync/Async](https://blogs.msdn.microsoft.com/csliu/2009/08/27/io-concept-blockingnon-blocking-vs-syncasync/) * [Why Non-Blocking?](https://techblog.bozho.net/why-non-blocking/) * [SQL and NoSQL](https://www.upwork.com/hiring/data/sql-vs-nosql-databases-whats-the-difference/) -* [Consistent Hashing - Explained by Tom White, author of 'Hadoop: the Definitive Guide'](http://www.tom-e-white.com/2007/11/consistent-hashing.html) +* [Consistent Hashing - Tom White, author of 'Hadoop: the Definitive Guide'](http://www.tom-e-white.com/2007/11/consistent-hashing.html) * [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) @@ -44,6 +44,7 @@ Contributions are always welcome! * [Use Solid Technologies - Don’t Re-invent the Wheel - Keep It Simple!](https://medium.com/@DataStax/instagram-engineerings-3-rules-to-a-scalable-cloud-application-architecture-c44afed31406) * [Performance is a Feature](https://blog.codinghorror.com/performance-is-a-feature/) * [Writing Code that Scales](https://blog.rackspace.com/writing-code-that-scales) +* [(UI) Design Doesn’t Scale - Stanley Wood, Design Director at Spotify](https://medium.com/@hellostanley/design-doesnt-scale-4d81e12cbc3e) * [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](https://docs.microsoft.com/en-us/azure/architecture/guide/design-principles/self-healing)