-
“Twitter has to effectively rebuild its system while it is still running — what other companies have described as “repairing an airplane in mid-air.” But I don’t think it’s fair to blame Scoble & LaPorte. They’re not doing anything wrong.
-
“Twitter’s core team may have had no way of foreseeing today’s issues, companies in the future should learn from this and choose the correct architecture while taking the time to think about scalability, just in case they do hit it big.”
-
“Twitter was originally architected not as a messaging service, but rather as a kind of CMS. That’s why Twitter has had major scaling issues over the past year or so — issues we’ve all experienced in both the system being down and general slowness.”
-
Twitter says: “Our key problems have been primarily architectural & growing infrastructure to keep up with growth. Working in Ruby has been, in our experience, a trade-off between developer speed/productivity and VM speed/instrumentation/visibility.”
-
“Copenhagen Consensus” — a menu for getting the most advancement of the human condition out of an extra (hypothetical) $75 billion over four years.”
If you liked my post, feel free to subscribe to my rss feeds
BlogoSquare
One Comment