Re:Creative Cloud outage leaves Adobe users unable to work
by e12e on Friday May 16, 2014 @09:50AM
(#7755466)
> Does it boil down to "single point of failure are bad"?
In the sense that "trust in a single entity as a single point of failure" - sure. Adobe can cut you off for any number of reasons, an outage being just one.
> When S3 is down, I don't remember seeing more than a few comments in the 'you should have self hosted your data' line
.
One of those comments might have been mine. Still, I'm not saying that you should self-host, I'm saying you should use solutions that you could realistically self-host should the need arise.
So if you use s3 for your (non-web-related) data, maybe have riak-cs ready to go as a backup (it's a bit of a contrived example, because you probably either need a "cloud fs" of some sort, or mercurial/git or whatnot, not "s3" to be able to keep working).
I absolutely think one should have an alternative ready if one is heavily based on amazon -- at least have the option to spin up a minimal set of equivalent services as an openstack/nebula solution.
There are many reasons why you might get into trouble with any one provider, not just that their infrastructure goes down. If they hold all your data (and your backups) -- you pretty much have no leverage at all.
In the sense that "trust in a single entity as a single point of failure" - sure. Adobe can cut you off for any number of reasons, an outage being just one.
> When S3 is down, I don't remember seeing more than a few comments in the 'you should have self hosted your data' line .
One of those comments might have been mine. Still, I'm not saying that you should self-host, I'm saying you should use solutions that you could realistically self-host should the need arise.
So if you use s3 for your (non-web-related) data, maybe have riak-cs ready to go as a backup (it's a bit of a contrived example, because you probably either need a "cloud fs" of some sort, or mercurial/git or whatnot, not "s3" to be able to keep working).
I absolutely think one should have an alternative ready if one is heavily based on amazon -- at least have the option to spin up a minimal set of equivalent services as an openstack/nebula solution.
There are many reasons why you might get into trouble with any one provider, not just that their infrastructure goes down. If they hold all your data (and your backups) -- you pretty much have no leverage at all.