Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Google Cloud networking issues in us-east1

status.cloud.google.com

Post reply on HN
Print view View original

101–110 of 341 posts

Re: Google Cloud networking issues in us-east1

#101

Post by CaptainJustin »

mathattack wrote: post #91
tscanausa wrote: post #87

Earlier quoted context omitted.

Terrance here from Google Cloud Support. There are only 3 things I can say about this situation. 1) These issues are currently unrelated. 2) We learn a lot from these situations. 3) A lot of these types of issues can be mitigated by running in more then 1 region. I really cant promise that today's situations will never happen again. There are a lot of moving pieces in our system and sometimes there are things outside…

“You should be using more than 1 region” could also be “you should be using more than one provider”, no?

It's quite common in cloud solution design to design for failure. One of the common assumptions that we hold to is that one region may go down. Other examples: Assume an instance of an app can go down. Assume a VM can go down. Assume a DC can go down.

This is not to excuse the downtime in any way.

Re: Google Cloud networking issues in us-east1

#102

Post by dkhenry »

_Codemonkeyism wrote: post #95
mathattack wrote: post #91

Earlier quoted context omitted.

“You should be using more than 1 region” could also be “you should be using more than one provider”, no?

Yes.

I have an awesome demo I give running a complex stateful workload across cloud providers to show off the system that I work on. What I have learned from giving that presentation many times is that while it is nice to say you can run cross cloud, for most workloads you should just pick one cloud, and be able to move to another provider if you ever need to.

Re: Google Cloud networking issues in us-east1

#103

Post by opportune »

benbro wrote: post #98
_Codemonkeyism wrote: post #95

Earlier quoted context omitted.

Yes.

Is it practical to use several providers when egress is so expensive?

No, not unless you are someone like Netflix. Usually you can configure multi-region failover and such and that will keep your things running. It is more expensive but for most use cases I think the cost is still less than the dev time/complexity of setting up multi-provider workflows and the inevitable duplication of resources (which is part of the cost of multi-region anyway)

Re: Google Cloud networking issues in us-east1

#104

Post by _wmd »

benbro wrote: post #98
_Codemonkeyism wrote: post #95

Earlier quoted context omitted.

Yes.

Is it practical to use several providers when egress is so expensive?

You can move 1.6TB between providers in a month for the same price as a single beefy DB server (m4.16xlarge here). That's a whole lot of logical replication..

Re: Google Cloud networking issues in us-east1

#105

Post by acomjean »

samcday wrote: post #69
tdhoot wrote: post #22

Earlier quoted context omitted.

Doubt Calendar is hosted on GCP. Generally Google does not run first-party systems on GCP, instead putting them on Borg (internal cloud).

Which, IMO, is actually a big problem. AFAIK Amazon are running a lot of actual production loads on AWS. Dogfooding can be extremely valuable, especially if a massive portion of your staff have the same profession as your target market. I've been using Google Cloud in a new role I started recently. There's definitely some parts of GCP I like, but whenever I use the Web Console I get the distinct impression nobody at…

yeah. With google maps I ran into this little bug when trying to get a new key/update my payments info like they forced all google map users to do.

The UI was maddeningly obtuse. This is from the second time I tried.. They did fix it eventually.

Very complex system for distributing new keys taking payments.

https://issuetracker.google.com/issues/124188941

Re: Google Cloud networking issues in us-east1

#106

Post by WaxProlix »

keepper wrote: post #86
samcday wrote: post #69

Earlier quoted context omitted.

Which, IMO, is actually a big problem. AFAIK Amazon are running a lot of actual production loads on AWS. Dogfooding can be extremely valuable, especially if a massive portion of your staff have the same profession as your target market. I've been using Google Cloud in a new role I started recently. There's definitely some parts of GCP I like, but whenever I use the Web Console I get the distinct impression nobody at…

It took amazon over over 6 years to do so though. EC2 was released in 2006. Amazon.com last non ec2 server was 2012. But a lot of features of amazon.com still don't run on the main AWS offerings. GCP has not been out for that long. Also, quite easier to run an e-commerce site than to run the web's largest search engine as well as the largest email provider, as well as the largest maps provider. Each of these has an o…

Large parts of AWS don't run on AWS either, due to issues with circular dependencies and similar problems. Similarly, if all of AWS onboards to use your AWS service, suddenly that's the business. Your 'real' customers and their traffic are dwarfed by the rest of AWS, making it hard to keep those real customers at the forefront. There's also an issue with those deps of cascading failures; having two separate fabrics/strata for internal and external offerings is similar to having a multi-regional offering in that it's more robust to random failures and such.

Re: Google Cloud networking issues in us-east1

#107

Post by stingraycharles »

BurritoAlPastor wrote: post #100
mathattack wrote: post #91

Earlier quoted context omitted.

“You should be using more than 1 region” could also be “you should be using more than one provider”, no?

Well, sure, if you hate your devops team and you want to make sure they can’t use any of the proprietary functionality of either provider. At which point, if you want to be managing a fleet of vanilla Linux boxes yourself, why use a cloud provider at all?

This seems overly negative. There are lots of ways to do hybrid clouds, especially if you’re doing it for only the more critical parts of your application.

Re: Google Cloud networking issues in us-east1

#109

Post by lern_too_spel »

crusader76 wrote: post #93
tomschlick wrote: post #80

Earlier quoted context omitted.

Spotify is hosted on google cloud: https://www.wired.com/2016/02/spotify-moves-itself-onto-goog...

I think the point OP was trying to make was relating to google services and their dependencies on each other.

I have the opposite conclusion as OP. Google doesn't use Google Cloud for anything critical, so I wouldn't use Google Cloud for anything critical or services that run on Google Cloud for that matter.

Re: Google Cloud networking issues in us-east1

#110

Post by mathattack »

BurritoAlPastor wrote: post #100
mathattack wrote: post #91

Earlier quoted context omitted.

“You should be using more than 1 region” could also be “you should be using more than one provider”, no?

Well, sure, if you hate your devops team and you want to make sure they can’t use any of the proprietary functionality of either provider. At which point, if you want to be managing a fleet of vanilla Linux boxes yourself, why use a cloud provider at all?

Staying on current versions, and the ability to scale usage up and down?
Post reply on HN