Some guy wrote a rant that his Google G-Mail account got disabled. So he used the Contact Us form to alert Google. He swore that he used a secure password. Therefore he doubts that his password was compromised. Google responded that they were looking into the problem.
In the end, the poor dude lost all his G-Mail history. This falls under the general risk of keeping your data in the cloud. I understand how easy this can be. Google has huge amounts of disk space. They have a nice and free product for you to use. You start using it and don’t look back. But you have to plan for the work case. That’s what I do.
You do not have to move away from the cloud to minimize the risks associated with it. For example, you can keep more than one Google account. That way you can split some of your email across multiple failure points. Yes this might cause some overhead while you check multiple accounts. However you can also use one account to aggregate mail from all the others.
The example guy from this story also lost his blog. This is something that is dear to me. I have spent the good part of a year blogging hard. I would hate for all that to go to waste. That’s why I have moved away from creating multiple blogs under one Google account. I am at the point where I create a new account each time I create a new blog. This is done even if I am working on a throw away blog.
I expect these problems to become more common as the industry embraces and moves into cloud computing en masse. You would be wise to assume that everything on the cloud will fail. The earlier you prepare for such a pending disaster, the better off you will be.
Mysterious Double Instance Hampering Performance - I study the existing code base. Confer with a colleague. Then I determine the optimal plan to change the functionality to load only a slice of all the dat...