mirror of
https://github.com/binhnguyennus/awesome-scalability.git
synced 2025-01-24 04:51:00 -05:00
Make Performance Part of Your Workflow
This commit is contained in:
parent
edba01d5bc
commit
90b1f2f7c2
@ -30,7 +30,7 @@ Contributions are always welcome!
|
|||||||
* [CAP Theorem and Trade-offs](http://robertgreiner.com/2014/08/cap-theorem-revisited/)
|
* [CAP Theorem and Trade-offs](http://robertgreiner.com/2014/08/cap-theorem-revisited/)
|
||||||
* [CAP Twelve Years Later: How the "Rules" Have Changed (2012) - Eric Brewer (VP of Infrastructure at Google)](https://www.infoq.com/articles/cap-twelve-years-later-how-the-rules-have-changed)
|
* [CAP Twelve Years Later: How the "Rules" Have Changed (2012) - Eric Brewer (VP of Infrastructure at Google)](https://www.infoq.com/articles/cap-twelve-years-later-how-the-rules-have-changed)
|
||||||
* [Scale Up or Scale Out, What it is and Why You Should Care](https://www.brianjgraf.com/2013/05/17/scalability-scale-up-scale-out-care/)
|
* [Scale Up or Scale Out, What it is and Why You Should Care](https://www.brianjgraf.com/2013/05/17/scalability-scale-up-scale-out-care/)
|
||||||
* [Scaling Up vs. Scaling Out: Hidden Costs](https://blog.codinghorror.com/scaling-up-vs-scaling-out-hidden-costs/)
|
* [Scaling Up vs Scaling Out: Hidden Costs](https://blog.codinghorror.com/scaling-up-vs-scaling-out-hidden-costs/)
|
||||||
* [ACID and BASE](https://neo4j.com/blog/acid-vs-base-consistency-models-explained/)
|
* [ACID and BASE](https://neo4j.com/blog/acid-vs-base-consistency-models-explained/)
|
||||||
* [Blocking/Non-Blocking and Sync/Async](https://blogs.msdn.microsoft.com/csliu/2009/08/27/io-concept-blockingnon-blocking-vs-syncasync/)
|
* [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/)
|
* [Why Non-Blocking?](https://techblog.bozho.net/why-non-blocking/)
|
||||||
@ -48,6 +48,7 @@ Contributions are always welcome!
|
|||||||
* [Scalability Worst Practices](https://www.infoq.com/articles/scalability-worst-practices)
|
* [Scalability Worst Practices](https://www.infoq.com/articles/scalability-worst-practices)
|
||||||
* [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)
|
* [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/)
|
* [Performance is a Feature](https://blog.codinghorror.com/performance-is-a-feature/)
|
||||||
|
* [Make Performance Part of Your Workflow](https://codeascraft.com/2014/12/11/make-performance-part-of-your-workflow/)
|
||||||
* [Writing Code that Scales](https://blog.rackspace.com/writing-code-that-scales)
|
* [Writing Code that Scales](https://blog.rackspace.com/writing-code-that-scales)
|
||||||
* [AWS Do's and Don'ts](https://8thlight.com/blog/sarah-sunday/2017/09/15/aws-dos-and-donts.html)
|
* [AWS Do's and Don'ts](https://8thlight.com/blog/sarah-sunday/2017/09/15/aws-dos-and-donts.html)
|
||||||
* [(UI) Design Doesn’t Scale - Stanley Wood, Design Director at Spotify](https://medium.com/@hellostanley/design-doesnt-scale-4d81e12cbc3e)
|
* [(UI) Design Doesn’t Scale - Stanley Wood, Design Director at Spotify](https://medium.com/@hellostanley/design-doesnt-scale-4d81e12cbc3e)
|
||||||
|
Loading…
Reference in New Issue
Block a user