Live data from Hacker News

Snap commits $2B over 5 years for Google Cloud infrastructure

techcrunch.com

271–280 of 311 posts

Re: Snap commits $2B over 5 years for Google Cloud infrastructure

#271

Earlier quoted context omitted.

Why opt for Google if you're going to use containers in Kubernetes? You then become cloud agnostic. You can even move to your own datacenter at some point (relatively) easily. Dropbox built out their own environment (and did it migrating 500PB out of S3) [1] [1a]. As did Twitter [2]. And Facebook [3]. And GitLab [4] (too soon?) As well as Mixpanel [5]. Even Twilio is multi-cloud (last time I checked it was split betw…

Easily move? It seems to me that you have no serious experience in the real world. There's something called "data gravity", and the non-secondary issue of how to migrate a "live" system (in production) from one cloud to another over the course of typically several weeks. Moving from one cloud to another, even with containers, is never easy at large scale. (source: I have worked at AWS for 6 years, at VMware for 2, an…

Actually it is. I just moved about 35k instances and 6PB in s3, multiple many TB pg instamces from AWS to google. It is not that bad anymore. Containers and fast internet make it easyish

Re: Snap commits $2B over 5 years for Google Cloud infrastructure

#272

Earlier quoted context omitted.

Why opt for Google if you're going to use containers in Kubernetes? You then become cloud agnostic. You can even move to your own datacenter at some point (relatively) easily. Dropbox built out their own environment (and did it migrating 500PB out of S3) [1] [1a]. As did Twitter [2]. And Facebook [3]. And GitLab [4] (too soon?) As well as Mixpanel [5]. Even Twilio is multi-cloud (last time I checked it was split betw…

Easily move? It seems to me that you have no serious experience in the real world. There's something called "data gravity", and the non-secondary issue of how to migrate a "live" system (in production) from one cloud to another over the course of typically several weeks. Moving from one cloud to another, even with containers, is never easy at large scale. (source: I have worked at AWS for 6 years, at VMware for 2, an…

Actually it is. I just moved about 35k instances and 6PB in s3, multiple many TB pg instamces from AWS to google. It is not that bad anymore. Containers and fast internet make it easyish

Re: Snap commits $2B over 5 years for Google Cloud infrastructure

#273

Earlier quoted context omitted.

Why opt for Google if you're going to use containers in Kubernetes? You then become cloud agnostic. You can even move to your own datacenter at some point (relatively) easily. Dropbox built out their own environment (and did it migrating 500PB out of S3) [1] [1a]. As did Twitter [2]. And Facebook [3]. And GitLab [4] (too soon?) As well as Mixpanel [5]. Even Twilio is multi-cloud (last time I checked it was split betw…

Easily move? It seems to me that you have no serious experience in the real world. There's something called "data gravity", and the non-secondary issue of how to migrate a "live" system (in production) from one cloud to another over the course of typically several weeks. Moving from one cloud to another, even with containers, is never easy at large scale. (source: I have worked at AWS for 6 years, at VMware for 2, an…

Actually it is. I just moved about 35k instances and 6PB in s3, multiple many TB pg instamces from AWS to google. It is not that bad anymore. Containers and fast internet make it easyish

Re: Snap commits $2B over 5 years for Google Cloud infrastructure

#274

Earlier quoted context omitted.

Why opt for Google if you're going to use containers in Kubernetes? You then become cloud agnostic. You can even move to your own datacenter at some point (relatively) easily. Dropbox built out their own environment (and did it migrating 500PB out of S3) [1] [1a]. As did Twitter [2]. And Facebook [3]. And GitLab [4] (too soon?) As well as Mixpanel [5]. Even Twilio is multi-cloud (last time I checked it was split betw…

Easily move? It seems to me that you have no serious experience in the real world. There's something called "data gravity", and the non-secondary issue of how to migrate a "live" system (in production) from one cloud to another over the course of typically several weeks. Moving from one cloud to another, even with containers, is never easy at large scale. (source: I have worked at AWS for 6 years, at VMware for 2, an…

Also if I could down vote you for saying that person has no experience I would. You just have the data to say that other than not picking the details

Re: Snap commits $2B over 5 years for Google Cloud infrastructure

#275
post #165

Earlier quoted context omitted.

> And when EC2 falls over, like it tends to do a few times a year? Multi-AZ, multi-region complete failures are very, very rare. How often do you get a failure in your data center per year (that you notice)? > You're going to be writing a lot of the same fallover code if you're running on someone else's hardware, so why rent? The answer is in the question -- when rented things fall down and go boom™, your code runs a…

>Multi-AZ, multi-region complete failures are very, very rare. How often do you get a failure in your data center per year (that you notice)? First, if you don't notice some random/unexpected EC2 instance failures, you don't have a big EC2 deployment. Even though there is a lot of pomp and circumstance around the cloud, when it comes down to it, your instances are still on a physical server in a datacenter somewhere…

Snap is using appengine, which transparently manages scale, availability, resiliency, deployment, and so forth. It's a higher level of service than ec2. Thus many of the valid concerns you describe do not apply to snap, or are at least minimized.

( Work at Google cloud)

Re: Snap commits $2B over 5 years for Google Cloud infrastructure

#276
post #266
post #99

Earlier quoted context omitted.

I love Hacker News, where a random person can tell a company their $2 billion plan on infrastructure is "a really bad move" with authority

You comment would be stronger if you removed the snark and actually refuted the parent's points. If you want to refute the points refute them, but this kind of comment adds nothing to the discussion. The parent made some good points about scale and infrastructure. I've worked with infrastructure on many projects and I can't come up with a coherent argument why any of the parent's points are wrong. Can you?

I read his point as praise of comment actually.

Re: Snap commits $2B over 5 years for Google Cloud infrastructure

#277

Earlier quoted context omitted.

On the one hand - you're right. Google is good, I use GCP, they are competent and good to work with. On the other hand "someone who has an entire product devoted to that one area, and has many years of experience and is probably the largest provider on the planet for that service" also describes Enron at the time. Google's no Enron, but Size isn't the metric one should use.

Parent listed 3 metrics. I don't think it's fair to pull one out and attack that instead of the combination of all 3.

you are right but i meant to imply enron was all three, but i didnt write that.

Re: Snap commits $2B over 5 years for Google Cloud infrastructure

#278

Earlier quoted context omitted.

That's unfair. From what I can tell all the canines are on the mobile app development team.

The android app team consist probably mostly of whales. (observation based on the fluidity of their app)

mbasic.facebook.com if you really feel that need for speed :)

Re: Snap commits $2B over 5 years for Google Cloud infrastructure

#279

Earlier quoted context omitted.

Facebook reported $27 billion in revenue in 2016. Snap reported $400 million. You're talking two orders of magnitude lower than Facebook and almost three lower than Google. Snap simply does not have the resources to pour into custom data centers, even if they can raise $2 billion for infra over 5 years. Unless they have serious talent already, they're not going to match Google's massive 15 year investments by a long…

>"Snap simply does not have the resources to pour into custom data centers, even if they can raise $2 billion for infra over 5 years." They have 1800+ employees as disclosed in their filing. So clearly people resources are not a problem for SNAP. Do you believe its not possible to build 4 datacenter - 2 US, 1 EU and 1 APAC datacenter for 2 billion dollars? These are tangible assets that you can depreciate as well. Th…

Disclosure: I work for Google, but nowhere near Cloud, and I have no knowledge of this deal.

Quite apart from the dollar costs and human capital required to build and maintain a DC, there's the lead time required to build the thing, and I'd speculate that that's potentially a significant factor in Snap's decision. Perhaps Snap are looking at e.g. how quickly Pokemon GO scaled their operation, and they're thinking for whatever reason that they might need to do something similar?

Re: Snap commits $2B over 5 years for Google Cloud infrastructure

#280
post #184

Earlier quoted context omitted.

Completely wrong way to think about it. In fact, those companies are cases of fraud and lying , and we generally do not assume companies lie. When Google releases their quarterly earnings, we assume the numbers are correct, unless there is evidence to believe it's fraudulent.

Bear Stearns didn't fail due to fraud, it failed due to not adequately tracking and assessing the risk of its assets. It is worth noting that there have been serious allegations made a few weeks ago against Snap that they are lying on the S-1.

Link?
Post reply on HN