News for hackers. Stuff that matters.
Re:Why you should not use Google Cloud by nemothekid on Saturday June 30, 2018 @03:45PM (#17432417)
Yes, we have backups. The problem with `data` is not the fact I have backups, is that at a certain scale I will have so much data that "moving providers" could take on the order weeks.

If OP happened to me, sure yes I could have my entire infra on AWS/Azure/whatever else Terraform supports in an hour, maybe more to replace some of the tiny cloud specific features we use. But if it takes me a day to me to just move the data into Azure, thats an entire lost business day of productivity.

Re:Why you should not use Google Cloud by southerndrift on Saturday June 30, 2018 @05:25PM (#17432837)
If it takes weeks then you should choose a second provider where you can show up with your backup hard drives or whatever you use and plug them in. Moving data physically is an option.
Re:Why you should not use Google Cloud by rhizome on Saturday June 30, 2018 @05:51PM (#17432917)
"Never underestimate the bandwidth of a semi full of harddrives."
Re:Why you should not use Google Cloud by mooreds on Sunday July 01, 2018 @01:24PM (#17436501)
Re:Why you should not use Google Cloud by markbnj on Saturday June 30, 2018 @04:08PM (#17432530)
Note that I did not imply that restoring the service to a different project or provider would always be easy or fast (certainly in the case of very large data volumes it would be neither of those things). I was addressing the prospect of losing "years of work" as was stated in the OP. That sort of implies that most or all of what they did over that time is recorded only in the current state of the GCP project that was disabled, and that is a really terrifying position to be in.
Re:Why you should not use Google Cloud by pavs on Saturday June 30, 2018 @04:08PM (#17432529)
People usually end up using backup or move infrastructure on short notice in catastrophic situations, which is presumably rare. Days worth of work to bring back your business in catastrophic downtime - doesn't seem like a bad thing at all to me. If anything, it sounds like a very well organized development flow with very optimistic time-frame.