News for hackers. Stuff that matters.
Re:Why you should not use Google Cloud by mark-ruwt on Saturday June 30, 2018 @01:47PM (#17431805)
If maximum uptime is critical to the business, your infrastructure should be cross-provider.

I've been running three providers as peers (DO, Linode, Vultr) as a one-man shop for years, and I sleep better at night knowing that no one intern can fatfinger code that takes me offline.

Re:Why you should not use Google Cloud by PretzelFisch on Saturday June 30, 2018 @01:56PM (#17431854)
At that Point wouldn't hosting it yourself running on something like vmware vsphere be a simpler option? At least you would have a nice hardware abstraction and a consistent api to build your tooling on.
Re:Why you should not use Google Cloud by mark-ruwt on Sunday July 01, 2018 @05:37AM (#17434854)
I hear you. For me, the abstraction is the Linux distro. Build scripts abstract out creating a clean, secure box before installing any custom software, so regardless of the provider, every machine is exactly the same.
Re:Why you should not use Google Cloud by CSDude on Saturday June 30, 2018 @01:55PM (#17431850)
All those are VPS providers, it is hard when you use other services of vendors
Re:Why you should not use Google Cloud by mark-ruwt on Sunday July 01, 2018 @05:34AM (#17434850)
Agreed! My take is that you don't have to, you shouldn't.
Re:Why you should not use Google Cloud by nullgeo on Saturday June 30, 2018 @01:50PM (#17431822)
What kind of business do you run? Can you explain a bit about how your systems in different providers are connected?
Re:Why you should not use Google Cloud by mark-ruwt on Sunday July 01, 2018 @05:32AM (#17434842)
Surely! Our business is mainly an API that B-to-B customers consume. The strategy is to create identical "pods" in different cities across different providers on identical distros. Between Vultr, Linode, and DO, that's 20+ cities you could place a pod in the States alone. Each pod has a proxy up front, a database slave, and a pair of app server and cache machines.

Ignoring tweaks for international customers, each proxy is in an A record round-robin with health checks via Route 53. US-based requests get forwarded to one of the pods, and the proxy either handles the request with local servers, or points to servers in another pod if it has servers that are down. If any pod has a power outage or goes down for any reason, Route 53 automatically pulls the entire pod out of the rotation. If an entire provider goes dark, all of the pods get pulled out of the rotation, but all the others keep running.

Re:Why you should not use Google Cloud by nullgeo on Sunday July 01, 2018 @11:19PM (#17439115)
This is very cool. Where can I learn more about stuff like this, and what are the prerequisites for learning something like this? I have a BSc in CS and understand OSes and programming languages pretty well.
Re:Why you should not use Google Cloud by mark-ruwt on Monday July 02, 2018 @07:45AM (#17440850)
Posts on http://highscalability.com can get a bit hardcore, but there's a lot of great knowledge there.
Re:Why you should not use Google Cloud by nullgeo on Monday July 02, 2018 @04:04PM (#17444894)
Thanks a lot for your help!
Re:Why you should not use Google Cloud by ryan-c on Saturday June 30, 2018 @02:14PM (#17431944)
Your domain registrar can probably still hose you. Where's your DNS hosted?
Re:Why you should not use Google Cloud by mark-ruwt on Sunday July 01, 2018 @05:23AM (#17434811)
Very true! I have a script that automatically commits any DNS changes to source control, so if Route 53 bites it I could quickly move somewhere else, but you're right, on the off chance my registrar decides to vanish, there'll be some panicking.
Re:Why you should not use Google Cloud by Scarbutt on Saturday June 30, 2018 @02:08PM (#17431910)
you really can't compare switching between generic vps providers from switching between the big cloud providers that provide lots of more useful services.
Re:Why you should not use Google Cloud by mark-ruwt on Sunday July 01, 2018 @05:20AM (#17434804)
It is a very different model, but my take is that you shouldn't be building anything on one provider that you couldn't easily move over to another. Provider lock-in is scary.