6 ms·
It's the entire service, not a bunch of files. When Netflix went down due to AWS outage, could you image them just "restoring a backup" on rackspace and running
by roee 14y ago
It's the entire service, not a bunch of files. When Netflix went down due to AWS outage, could you image them just "restoring a backup" on rackspace and running just like that?
- sologoub 14y agoThe core service, sure. The problem is that Netflix accounts for something like a 3rd of US bandwidth consumption. Not many services can sustain that. Netflix also has to manipulate a giant library of assets. Doesn't sound like this is part of their service. A normal company should be able to fail-over. I have been experimenting a lot with Google App Engine. Failing over from a PaaS like that is not easy because your app typically relies on a bunch of proprietary APIs. However, it is possible, provided you keep right replication and architect the application accordingly. You also don't need to fail over 100% of your app. I don't have a very clear understanding of what Soluto actually does (sounds like a GotToAssist competitor), ability to fail over the part of the system that facilitates the remote desktop experience would be more important than administration or creation of new accounts. (This is a crude example.)
- deleted 14y ago[deleted]
- jspaur 14y agoI've got several services (both consumer and commerical) running on Azure and right now I just see some issues with storage in the south. Web/Worker, VMs, Sql, etc. are running just fine it appears. Any pointers on where I should be looking for potential issues?