3 ms·
You should probably reconsider hosting production sites on super-cheap VPSes with a 1:1 SLA refund. They're going to go down. And, when they do, you'll get th
by JohnTHaller 12y ago
You should probably reconsider hosting production sites on super-cheap VPSes with a 1:1 SLA refund. They're going to go down. And, when they do, you'll get the 7/10ths of a cent refund per hour promised for your $5 instance (1.4 cents per hour for $10, 2.8 cents per hour for $20, etc). But if you depend on a site for your business, ask yourself how much it costs you per hour of downtime and plan appropriately.
For context: I'm a happy Digital Ocean customer (as well as Rackspace and others). I like their services and consider them a great value for the money. I've also gotten multiple developer friends into using them. But I don't let them be a single point of failure for anything critical.
- kbar13 12y agodowntime is an issue no matter how much you pay your infrastructure provider. You should account for downtime in your application and your infra by taking advantage of low-hanging high availability fruit. Things like saltstack (saltstack.org) make this mega-easy.
- JohnTHaller 12y agoIt's easier for apps since you can build in failover support based on multiple servers pretty easily (I just implemented this in our 'live' installers recently on Windows). It's a bit harder at the website level for an average user, though. I know far too many people that have a single point of failure website on a super-cheap VPS that's just down whenever the VPS is down. Most of them would have no idea how to implement a load balancer and failover support. Though I could probably get them into something like CloudFare or similar.