Wednesday, July 21, 2010 | By Jean-Paul Cozzatti (@jeanpaul) [23:49 UTC]
On Monday, a fault in the database that stores Twitter user records caused problems on both Twitter.com and our API. The short, non-technical explanation is that a mistake led to some problems that we were able to fix without losing any data.
Thursday, July 15, 2010 | By Larry Gadea (@lg) [18:35 UTC]
Twitter has thousands of servers. What makes having boatloads of servers particularly annoying though is that we need to quickly get multiple iterations of code and binaries onto all of them on a regular basis. We used to have a git-based deploy system where we’d just instruct our front-ends to download the latest code from our main git machine and serve that. Unfortunately, once we got past a few hundred servers, things got ugly.