Four points, at least: 1) Google's set of hardware is likely way more reliable than mine, or anyone's on this list.
2) Improving performance in computing is all about chasing bottlenecks - We're going to have to do something about bandwidth to make external (private or public) clouds competitive with internal clouds. 3) Bandwidth also has to meet the reliability requirements for your purposes. BIFs are a bitch when it's your connection to your computing resources, rather than simple web/email stuff that just went bye-bye. 4) The security of clouds hosted by third parties is not yet tested. If you don't care (much) about your data being exposed to the world, and don't need (much) Internet bandwidth to keep your computing performant, and the risk to your org of connectivity outages is low, public clouds (whether it's Google Docs or something else) are probably just fine for you - actually probably better than what you can do in-house, because the risk of data actually being lost is lower than doing it yourself. $WORK has to care about its data - it deals with both engineering/product IP and extremely sensitive third party data. I will fight against any public cloud implementation until I'm satisfied on points 2, 3 and 4 - and I expect points 2 and to be considerably easier to deal with than point 4. Kurt On Wed, Aug 4, 2010 at 08:55, Stu Sjouwerman <[email protected]> wrote: > Anyone move from MS Office to Google Docs? > > I'm doing a WServerNews editorial about this. > > Anyone made the jump, and how did this pan out? > > Warm regards, > > Stu > > > > ... > > > > ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~
