Stuff The Internet Says On Scalability For April 8, 2011
Friday, April 8, 2011 at 9:23AM
HighScalability Team in hot links
Submitted for your reading pleasure on this tomato killing frosty morn...
Now we really know why vampires feed on blood...they are elastically acquiring more compute power. Your Next Computer May Be Made of...Blood! It's those memristors again. Ancient vamps are really just giant super computers.
10,000-core Linux supercomputer built in Amazon cloud By Jon Brodkin. The 10,000 cores were composed of 1,250 instances with eight cores each, as well as 8.75TB of RAM and 2PB disk space. The cluster ran for eight hours at a cost of $8,500.
Quotable Quotes for $273 Alex:
@davidklemke: Holy balls Windows Azure Tables is awesome. Man am I regretting not getting into this cloud stuff sooner, it's scalability heaven.
@nik: The volume of tweets we are flowing into HBase is truly staggering #bigdata #datasift
@wattersjames: One of the key points I mentioned before: Scalability is being able to deploy on the smallest systems that meets your req's
@swiftriver: Great #data quote: "More is not better. Better is better." #bigdata #datascience
@marcelomilo: YouTube is almost entirely written in Python. Oh! think of the scalability of a Python based system...
Resilience Engineering: Part I shows you just can't keep John Allspaw down. The core idea: builders of safe complex systems must embrace the messiness of the human element, not just blame all failures on our lack of machine like qualities: it's better to ask why humans could make an error than to blame humans for the error; complex failures do not originate from linear causes; learn from what goes right; optimize for recovery time, not failure interval; safety is adaptation. For information about resiliency in a larger context take a look at Resilient Communities.
Guy Steele & Richard Gabriel: 50 in 50. Either the strangest beat poetry you've ever heard or the stragest programming language history you've ever heard. In either case, it's interesting.
Cliff Click of Azul Systems knows his stuff. In A JVM Does That? he reveals the 5 illusions of the JVM. These illusions allow programmers to think: bytecodes are fast and have a reasonable cost model, you can quickly change the program at any time, infinite memory, consistent threading and memory model, quick time access, that these other illusions all work on all sorts of machines from cell phones. But we want to be beguiled even further with illusions of infinite Stack, code is data, Integers are as cheap as ints, memory supports atomic update, a JVM run utterly different languages. Remember we just wanted mirrors that gave us the illusion of youth and beauty? Also take a look at Clojure: STMs vs Locks.
Virtualization and IO Modes = Extra Complexity By Peter Zaitsev. The point is Virtualization adds complexity and there are at least some cases when you may be lied to about IO completion.
Level-triggered and edge-triggered by Mike Burr. In a distributed system you should move state information, not work items. Distribute information about the desired state and let each node determine how best to get to that state.
Can Rob Kalin Scale Etsy? "We want to allow the makers of the world to claim authorship for what they're making. This is what Etsy stands for: The little guy being able to organize a better marketplace."