Hey, it's HighScalability time:

(Ukrainian daredevil scaling buildings)

• 877,000 TPS: Erlang and VoltDB. 
• Quotable Quotes:
  • Hendrik Volkmer: Complexity + Scale => Reduced Reliability + Increased Chance of catastrophic failures
  • @TheRealHirsty: This coffee could use some "scalability"
  • @billcurtis_: Angular.js with Magento + S3 json file caching = wicked scalability
  • Dan Milstein: Screw you Joel Spolsky, We're Rewriting It From Scratch!
  • Anil Dash: Terms of Service and IP trump the Constitution
  • Jeremy Zawodny: Yeah, seek time matters. A lot.
  • @joeweinman: @adrianco proves why auto scaling is better than curated capacity management. < 50% + Cost Saving
  • @ascendantlogic: Any "framework" naturally follows this progression. Something is complex so someone does something to make it easier. Everyone rushes to it but needs one or two things from the technologies they left behind so they introduce that into the "new" framework. Over the years everyone's edge cases are accounted for with frameworks on top of frameworks and suddenly everyone is looking for the next big simplification.
• Imagine if you had a beowulf cluster of tiny antennas? You could build a TV rebroadcasting service that has old media running for the Galt's Gulch of pay TV.
• As a technologically advanced nation, why haven't we done this yet? Nationwide Google Fiber would cost $11B over five years, probably will never happen. I say this while using my nation wide power/telephone/road/defense system.
• Great list of technical talks. I'm partial to Big Ball of Mud.
• Making Black Swans work for you: Stick to simple rules; Decentralize; Develop layered systems; Build in redundancy and overcompensation; Resist the urge to suppress randomness; Ensure everyone has skin in the game; Give higher status to practitioners rather than theoreticians.

Don't miss all that the Internet has to say on Scalability, click below and become eventually consistent with all scalability knowledge...