Whoops. That seems to be exactly what happened again yesterday.

Foursquare:

In a nutshell, the same thing happened: an overloaded database, the solution to which again was manually redistributing check-in data to make sure no databases were overburdened and then rebooting the site, which we were finally able to do after nearly six hours of downtime. Unacceptably and frustratingly long, again.

The service isn’t being quite so bold this time in predicting smooth sailing going forward. While they they have some new safegaurds in place, this time they’re just saying “We’re hoping that these changes will help to stabilize things going forward.“

While they’ve had a very rough couple of days, Foursquare is still not close to the downtime Twitter experienced while it was growing. Hopefully the relatively small team (32 people) can work this out. At least they’re being open about the problems and communicating well — follow along here and here.

0 0

1 1 2 2 3 3 4 4 5 5 6 6

Authors: MG Siegler

to know more click here