Hacker News Reader

Everything fails. Design systems that minimize the impact failures have on your customers. Moving to another provider isn't going to fix the problem. Data like this should be stored in more than one place.

View on HN

In reality, replicating across two clouds is difficult and expensive. It's quite possible that Bitbucket wouldn't exist at all if they had used such an architecture.

I'm looking at cassandra as a possible solution for things like this.

Seems like a popular theme right now -- one of the github guys is working on a cassandra git backend at http://github.com/schacon/agitmemnon, and paul querna of ASF infrastructure is looking at doing the same for svn.

That's an over generalization. And difficult and expensive relative to what? When evaluating the cost of solutions to problems like this, the basic idea is to compare the cost of the solution and the cost of the problem (if realized) with the likelihood of the problem being realized factored in.

It's quite possible Bitbucket will cease to exist if they continue to have problems like this. I'm sure their customers are not happy. It does sound like they have plans to fix this once they get back up and running.

Reply on news.ycombinator.com