The email sent will contain a link to this article, the article title, and an article excerpt (if available). For security reasons, your IP address will also be included in the sent email.
It's HighScalability Time:
- @davilagrau: Youtube, GitHub,..., Are cloud services facing a entropic limit to scalability?
- Async all the way down? The Tyranny of the Clock: The cost of logic and memory dominated Turing's thinking, but today, communication rather than logic should dominate our thinking. Clock-free design uses less than half, about 40%, as much energy per addition as its clocked counterpart. We can regain the efficiency of local decision making by revolting against the pervasive beat of an external clock.
- Why Google Compute Engine for OpenStack. Smart move. Having OpenStack work inside a super charged cloud, in private clouds, and as a bridge between the two ought to be quite attractive to developers looking for some sort of ally for independence. All it will take are a few victories to cement new alliances.
- 3 Lessons That Startups Can Learn From Facebook’s Failed Credits Experiment. I thought this was a great idea too. So what happened? FACEBOOK DID NOT ENCOURAGE SHARING — IF CONSUMERS DON’T HAVE A REASON TO SHARE, THEY WON’T; FACEBOOK NEVER MADE A CASE FOR CARING ABOUT CREDITS; FACEBOOK DISCOURAGED ITS PARTNERS (DEVELOPERS) FROM SUPPORTING CREDITS.
- Some patterns for fast Python by Guido van Rossum: Avoid overengineering datastructures; Built-in datatypes are your friends; Be suspicious of function/method calls; Don't write Java (or C++, or Javascript, ...) in Python; Are you sure it's too slow? Profile before optimizing!; The universal speed-up is rewriting small bits of code in C. Do this only when all else fails. Great discussion in the comments.
Don't miss all that the Internet has to say on Scalability, click below and become eventually consistent with all scalability knowledge...
Return to Article