I wasn’t expecting to do a video interview. I hadn’t had any sleep in 30 hours. I was tired and had just finished a dress rehearsal for our new “WorkFast.tv” show that we’re filming at Revision 3 and after that I was on Gillmor Gang, who had FriendFeed’s founders on. The show isn’t up yet, but is a very interesting one.
Scoble winds up recording part of the discussion into an interview that you can now view on qik.com.
In the meantime, Mike Arrington has a few harder-hitting questions:
* Is it true that you only have a single master MySQL server running replication to two slaves, and the architecture doesn’t auto-switch to a hot backup when the master goes down?
* Do you really have a grand total of three physical database machines that are POWERING ALL OF TWITTER?
* Is it true that the only way you can keep Twitter alive is to have somebody sit there and watch it constantly, and then manually switch databases over and re-build when one of the slaves fail?
* Is that why most of your major outages can be traced to periods of time when former Chief Architect/server watcher Blaine Cook was there to sit and monitor the system?
* Given the record-beating outages Twitter saw in May after Cook was dismissed, is anyone there capable of keeping Twitter live?
* How long will it be until you are able to undo the damage Cook has caused to Twitter and the community?
With stories like this on a weekend – who really needs Twitter? Just read the bitchmeme…
Feeling stuck in self-doubt?
Stop trying to fix yourself and start embracing who you are. Join the free 7-day self-discovery challenge and learn how to transform negative emotions into personal growth.