|
|
|
|
|
by Xylakant
4932 days ago
|
|
I don't use gmail either, but if "frozen out of everything" is you concern go and use the imap connector to integrate gmail into the local mail program of your choice. From there on the failure mode is about the same as you'd expect from any other mail server - and I'd bet that gmails uptime is about on par or better than any other mail-service you can get out there, including your own server. |
|
I see this argument a lot, and there is truth in it.
However, there is a key difference. My own machine's uptime is certainly lower, but I have some control over when the downtime is.
Google chose to push a change that accidentally broke things. If I have a critical deadline, I can choose not to push any changes to my systems at all. When you use a cloud provider, you lose this choice.
So the question isn't really about comparing uptimes as a single figure any more. What about uptime during defined critical periods?
Edit: people replying seem to have inferred that I'm saying that running your own email server is better than using Google Apps. I didn't say that. I'm just saying that in any comparison, there is more to "cloud" reliability than a single uptime figure, and so using a single uptime figure comparison is not helpful in such a debate. The control you have over update timing is an important consideration to make in the general "move to the cloud" case.