Why the “Digital Ocean killed my company” incident scares the hell out of me
101–110 of 185 posts
Re: Why the “Digital Ocean killed my company” incident scares the hell out of me
#102Earlier quoted context omitted.
> But I still do business with DO because it costs ~half the price of a comparable EC2 instance I'm curious why people who don't have massive scaling and variability issues choose DO or AWS for their hosting. For 34€/month, Hetzner will rent you a physical server (i7-6700, 64GB RAM, 2x512GB SSD, 1Gbit/s networking). That's a monster of a machine and can run most sites out there. And if you need more oomph and better…
In our case, because it was easy to get thousands of dollars of free credit in Google cloud (the same appeared to be true for AWS). This went up to tens of thousands for Series A. We had zero serving costs and would have continued to do so for years. It makes perfect sense for Google/Amazon to incentivise startups to design themselves for their cloud.
Can you share how?
Re: Why the “Digital Ocean killed my company” incident scares the hell out of me
#103Earlier quoted context omitted.
No reason to. If your cloud provider does your DNS and you switch to a different cloud provider... ...then just set your registrar to point to the new DNS provider. You've still got total control.
That transition requires authorisation from the original provider. If they locked your account and don't pick up the phone, you won't get the move approved and won't be able to repoint your urls to a different cloud.
Re: Why the “Digital Ocean killed my company” incident scares the hell out of me
#104Test moving your environment between service providers in production.
You should be able to failover from one provider to another, in a predictable way. You should actually do so every few months so that you're well versed in what needs to happen. If you practice this, you will be prepared in case the absolute worst happens.
Re: Why the “Digital Ocean killed my company” incident scares the hell out of me
#105Earlier quoted context omitted.
$200/mm for a 10MM ARR company. Can you add more info here. What sort of app/company are we taking about here? Genuinely curious
For production, $200/mo. Dev/testing seem to always cost 3x+ what production servers cost. One was an IT management/automation SAAS company (I think they were $450/mo), another was backoffice SAAS company (I think they were $1000/mo but they were also hosting for an independent dealer of their SAAS so it was two production systems, and 10 years of tech debt), third is a live video consultancy SAAS that outsourced the…
Re: Why the “Digital Ocean killed my company” incident scares the hell out of me
#106I've got a stable setup: --------------------------------------- Vultr ========================== Linode --------------------------------------- Los Angeles ==================== Dallas Mastercard 1234 ============= Visa 4567 --------------------------------------- VMs with custom Linux (ROOT/ZFS Debian) Replicating snapshots every 5 minutes CloudFlare + HAProxy Load Balancing Total cost: 6 VMS at $20 each: $120, Clou…
Re: Why the “Digital Ocean killed my company” incident scares the hell out of me
#107Earlier quoted context omitted.
In our case, because it was easy to get thousands of dollars of free credit in Google cloud (the same appeared to be true for AWS). This went up to tens of thousands for Series A. We had zero serving costs and would have continued to do so for years. It makes perfect sense for Google/Amazon to incentivise startups to design themselves for their cloud.
>because it was easy to get thousands of dollars of free credit in Google cloud (the same appeared to be true for AWS) Can you share how?
Re: Why the “Digital Ocean killed my company” incident scares the hell out of me
#108Earlier quoted context omitted.
Most $10MM ARR startups are running on two medium T class aws instances behind a load balancer at $35/mo plus another small server for accessories (redis, message queue, etc) and then a sql backend. That's something like $200/mo for infrastructure, you never need to maintain the hardware and you have the option to autoscale at any time to support $100MM ARR. Plus you get access to backups and all the other tools and…
You’re telling me that 10 million dollar “startup” companies can’t run 1 server without incurring “years” of tech debt? Sorry, that just sounds unbelievable.
Re: Why the “Digital Ocean killed my company” incident scares the hell out of me
#109Earlier quoted context omitted.
That's wishful thinking. If there's state in that virtual machine, it's probably either stored on the physical host or in a SAN. If it's in the physical host, it has to be fished out of that machine or restored from a backup. If it's a SAN, you can lose your virtual machine if the SAN goes down. I've seen both happen. Actually, a single machine with RAID is surprisingly stable. A provider like Hetzner can switch out…
>If there's state in that virtual machine, it's probably either stored on the physical host or in a SAN I think the point is to write your application in a way that there's not state in the VM. My VMs are disposable and in fact the way I do deployments is to spin up a new VM in DO and then assign it the floating IP for production. If things go haywire I can easily swap back the IP address to the known good VM.
Re: Why the “Digital Ocean killed my company” incident scares the hell out of me
#110I've had a DO mistake take down my site before, and when it was brought back up it had been reverted to several months prior. DO support was at a loss as to why this would have happened. I tried to restore from DO's backup service, but their backups had apparently stopped running several months prior as well. This was a major issue and could have easily been the death of my company, all because of a DO glitch. But it…
If you don't mind me asking, what is the preferred method to backup to S3? Is it possible to scp or rsync a mysqldump to S3 or do you install aws tools on DO and run aws s3 cp as a scheduled job?
https://docs.aws.amazon.com/cli/latest/userguide/cli-chap-in...