4 ms·
A response to this article on Redis: http://aphyr.com/posts/283-call-me-maybe-redis http://aphyr.com/posts/283-call-me-maybe-redis
by nutmeg 13y ago
A response to this article on Redis: http://aphyr.com/posts/283-call-me-maybe-redis http://aphyr.com/posts/283-call-me-maybe-redis
- keeran 13y agoHis continued use of "CP" confused me for a while, so TIL about CAP Theorem http://en.wikipedia.org/wiki/CAP_theorem http://en.wikipedia.org/wiki/CAP_theorem
- bretthoerner 13y agoAnd better: http://henryr.github.io/cap-faq/ http://henryr.github.io/cap-faq/
- krenoten 13y agoIf you have the time, this video by Basho's CTO will give you a much better understanding of the tradeoffs that are involved in distributed system design: http://www.infoq.com/presentations/Concurrency-Scale-Distributed http://www.infoq.com/presentations/Concurrency-Scale-Distrib... A great alternative to thinking about things in terms of CAP that Justin brings up is harvest-yield, where yield is the probability of completing a request and harvest is the fraction of your data that the response actually represents. Here's the paper: http://lab.mscs.mu.edu/Dist2012/lectures/HarvestYield.pdf http://lab.mscs.mu.edu/Dist2012/lectures/HarvestYield.pdf
- lacksconfidence 13y agohmm, i'm not sure how it could be better worded, but since antirez already links to this, i had thought you were posting a response to antirez's comments