If you're reading this and concerned for your own backup story, fret not! In 2019 secure off-premise backups are super easy to implement, even for a 1 person shop. Get something like Restic or Borg or any one of the enumerated options here: https://github.com/restic/others I've recently implemented backups with Restic, the static binary and plethora of supported storage backends was extremely appealing. The easiest s…
"DigitalOcean Killed Our Company"
371–380 of 620 posts
Re: "DigitalOcean Killed Our Company"
#372Earlier quoted context omitted.
DO has shown that their service is simply not suitable for some use cases: those that impose an "unreasonable" load on their infraestructure. Even worse: they don't explicitly state what is considered "unreasonable". So, if your business is serious, you have to assume the worst-case scenario: DO can't be used for anything Conclusion: Digital Ocean is just for testing, playing around, not suitable for production.
> Conclusion: Digital Ocean is just for testing, playing around, not suitable for production. I think that's always been the standard position most people take. DO, Linode, etc are for personal side projects, hosting community websites, forums etc. They are not for running a real business on. Some people do, sure but if hosting cost is really that big a portion of your total budget you probably don't have a real busi…
Re: "DigitalOcean Killed Our Company"
#373Earlier quoted context omitted.
For some practical, if extreme, examples: if a customer were to host a phishing site, or a site hosting CP, it would be grossly irresponsible (and likely even illegal) for the hosting provider to retain the customer's data after account suspension and allow them to download it.
When this happens they should contact law enforcement, not play god.
And do what in the mean time? The legal system acts slowly. In the age of social media outrage, would you allow the headline "Digital Ocean knew they were serving criminals, and they didn't stop them" if you were CEO?
It's easy to be outraged when these systems and procedures are used against the innocent. That does not mean we should stop using rational thought. If someone is using DO to cause harm, then DO should (be allowed to) stop the harmful actions.
Re: "DigitalOcean Killed Our Company"
#374Earlier quoted context omitted.
Probably because of publicity. How many of those companies went bankrupt silently, because their case did not cause much attention in news?
Accidents can happen. Don't really blame Digital Ocean for the accidental locking but this response is insane: https://pbs.twimg.com/media/D76ocofXoAY_xB5.png
Re: "DigitalOcean Killed Our Company"
#375Earlier quoted context omitted.
Old MSFT rule of thumbs was 2 bugs per day during bug crunch mode. Sounds crazy, but when you consider the number of "this text is wrong" and "that text box is too short" bugs that existed after a year of furious development, it wasn't too hard to achieve. Gotta hit that ZBB!
Per day? Or per hour?
Re: "DigitalOcean Killed Our Company"
#376Re: "DigitalOcean Killed Our Company"
#377Question : so what do you do besides host it yourself? Do you set up a backup on a different cloud service so that at least you can failover without too much downtime? you then have to at least pay for the some of the resources even if there is no traffic. or backup locally but have a process set up with the different service so you can provision and get back up quickly? or is there a better solution?
Re: "DigitalOcean Killed Our Company"
#378Some people on HN hate Linode because of their past security screwups (which is valid), but having used both DO and Linode quite a lot, the support on Linode is way, way, way better than DO's. DO's tier 1 support is almost useless. I set up a new account with them recently for a droplet that needed to be well separated from the rest of my infrastructure, and ran into a confusing error message that was preventing it f…
Does DO have different levels of support that you can pay for like AWS? I like that system. You pay when you need it. You pay more if you need more support. The difference in support DO vs Linode is probably due to DO being cheaper.
Re: "DigitalOcean Killed Our Company"
#379Earlier quoted context omitted.
> DO seems to have gone with the "hire cheap overseas support that almost but doesn't quite understand English" strategy, whereas the tier 1 guys at Linode have on occasion demonstrated more Linux systems administration expertise than I've got. That's simply not true. There's support engineers hired around the world, and depending on when your ticket is posted, someone awake at that time will answer. DO is super remo…
But, isn’t hiring all over the world exactly because it is cheaper for the same kind of talent. I’m sure the company doesn’t do it out of the goodness of their heart. Then of course, there is no guarantee these people speak and understand english perfectly.
The reality is that top talent, even if remote, is competitive whether they are in NYC/SFO/SEA or not. And DO has some pretty talented people on staff.
And then, having people in all timezones is definitely an advantage for 24/7 support. I'd say it's not negligible, and not an after thought.
Now about english fluency, it's only that important to english native locations. And really, most of tech does not necessarily have english as a first language - I certainly don't. So I'd say that encountering support engineers with imperfect english shouldn't be a problem to anyone, and definitely not a sign of cheap labor. In fact, I'd say bitching about someone's english proficiency in tech is kind of counterproductive and I find it discriminatory.
Anyways. DO doesn't hire international employees to get cheap labor, that's a preposterous proposition. And with datacenters around the world and a large presence and customer base, it makes sense to have staff on board from many of these areas. And that staff might answer your tickets at night when they're on shift. Shouldn't they?
Re: "DigitalOcean Killed Our Company"
#380Earlier quoted context omitted.
AWS has default instance limits too, though, which you need to open ticket to increase.
Which is a much better policy than suspending the account.. 10 instances is nothing!