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

Spotify moves its back end to Google Cloud

news.spotify.com

Post reply on HN
Print view View original

341–350 of 397 posts

Re: Spotify moves its back end to Google Cloud

#341

Post by latchkey »

chm wrote: post #250
latchkey wrote: post #35

What Google Cloud needs is a better sales story. AWS consistently beats out Google in this respect. This story is welcomed and there should be more success stories published like this. My business is a heavy GC user (AppEngine, Datastore, CloudStorage, BQ, ComputeEngine, ManagedVM) and I couldn't imagine achieving what we have achieved in such a short amount of time on any other platform. We (myself and another guy)…

I assume your business is GearLaunch? If so, why do I need to enable javascript just to see the landing page, which is just a logo...? I'm curious if this was intended, or a consequence of the framework you're using (e.g. Meteor). Edit: It seems to be on purpose, with the use of noscript tags.

It is 2016 and ok to run JavaScript, the Internet works much better with it. I promise not to hack your flip phone. =)

Re: Spotify moves its back end to Google Cloud

#342

Post by justinjlynn »

liveoneggs wrote: post #131
latchkey wrote: post #47

Earlier quoted context omitted.

Are you implying that we don't measure and test? We do and I'm very happy with the results. =) StackDriver, Google Cloud console, Intercom, Mixpanel and Pingdom are all being used as well.

If that's the case then you might actually be "doing devops". If pingdom is notifying you via sms then you may also be carrying a pager.

Indeed, I do wish we'd stop with all of the verbal gymnastics and just say we're doing ops correctly. "We don't do ops" usually means "We don't find ops to be troublesome because we do it correctly". No group of people needs dedicated janitorial staff if everyone picks up and dusts occasionally. Of course, you know what this implies.

Re: Spotify moves its back end to Google Cloud

#343

Post by dba7dba »

bshanks wrote: post #310
boulos wrote: post #76

Earlier quoted context omitted.

For Google Cloud products that have made it to General Availability (GA), we have a one-year deprecation policy ( https://cloud.google.com/terms/ , Section 7.2). That is, if we're going to make some big change, we give you a 1 year heads up. Disclaimer: I work on Compute Engine, but I'm not a lawyer ;).

Google seems to be facing a trust problem here that its competitors don't, due to its history of shutting down popular services, even those that were being used internally and even those that it had been recently hyping to the press. Due to this unusual context, perhaps it would help if Google were to increase this promise from 1 year to 10 years (or 5 years or 3 years).

Trust is hard to earn and easy to lose. No matter how much power/money you have at disposal.

Re: Spotify moves its back end to Google Cloud

#344

Post by ed_blackburn »

ed_blackburn wrote: post #14

I always used to think Facebook would make a move for Spotify..

-1 :(

Zuckerberg used to wax lyrically about Spotify and I always assumed Facebook would one day like to move to the subscription streaming market. A barrier to entry for Spotify to stream movies I always suspected would be cash.

Moving to google cloud won't stop a Spotify sale but it may discourage some?

Re: Spotify moves its back end to Google Cloud

#345

Post by ed_blackburn »

ed_blackburn wrote: post #14

I always used to think Facebook would make a move for Spotify..

-1 :(

Zuckerberg used to wax lyrically about Spotify and I always assumed Facebook would one day like to move to the subscription streaming market. A barrier to entry for Spotify to stream movies I always suspected would be cash.

Moving to google cloud won't stop a Spotify sale but it may discourage some?

Re: Spotify moves its back end to Google Cloud

#346

Post by Facens »

latchkey wrote: post #35

What Google Cloud needs is a better sales story. AWS consistently beats out Google in this respect. This story is welcomed and there should be more success stories published like this. My business is a heavy GC user (AppEngine, Datastore, CloudStorage, BQ, ComputeEngine, ManagedVM) and I couldn't imagine achieving what we have achieved in such a short amount of time on any other platform. We (myself and another guy)…

"profitable growth"?

:puzzled:

Re: Spotify moves its back end to Google Cloud

#347

Post by halayli »

vgt wrote: post #286
halayli wrote: post #166

Congrats to the sales team at Google Cloud. I wonder how much Google's new AI services played a role in convincing Spotify to use them.

Hey guys it's Tino. When will you contribute to our Big Data blog with your excellent ideas? :) https://cloud.google.com/blog/big-data/

I am more than happy to contribute but I have a feeling you've mistaken me with someone else? :)

Re: Spotify moves its back end to Google Cloud

#348

Post by jasey »

dlgeek wrote: post #312
snowwrestler wrote: post #294

Earlier quoted context omitted.

This is also my impression of Google compute offerings, but it's also my impression of AWS offerings. I mean, when people think of AWS services, do "service and stability" really come to mind? IME it's impossible to reach a person unless you're a multi-million-dollar org, and Amazon itself tells customers that AWS services can go down at any time and it's up to the customer to architect the application to deal with i…

> IME it's impossible to reach a person unless you're a multi-million-dollar org I am sorry to hear that, but I can assure you it's not the case. I'm an engineer on a newer (and therefore smaller) AWS service, and I help investigate customer complaints, from customers of all sizes, all the time. I'll also note that not only do we handle cases that come in via our paid support, we also do deep dives for customers who…

My experience with AWS has been exactly this. I had a Cognito question/issue on IOS that I posted to stack-overflow and got a quick response from an engineer at Amazon. Also I posted a support ticket (zero paid support) to increase my sns API calls limit (which didn't end up being required because I was doing it wrong) and they got back to me over a few days to a week.

On the other hand, Google takes my Android app off the play store with next to zero details on the reason why and I have next to zero methods to contact them. The only way I was able to get my app back was to remove features via trial and error to determine what part was infringing. Why would i partner with Google again for hosting?

Re: Spotify moves its back end to Google Cloud

#350

Post by boundlessdreamz »

boulos wrote: post #334
boundlessdreamz wrote: post #321

Earlier quoted context omitted.

GCE pricing is great but GCS is not. It is much more expensive than S3 or cloudfront (2.5x - 1.3x) when you consider per request costs. I have brought this up a couple of times on HN to Google cloud employees but nothing has changed. 1. https://news.ycombinator.com/item?id=10442654 2. https://news.ycombinator.com/item?id=10187600 Other problem areas for GCS compared to S3/Cloudfront 1. SSL support for custom domains…

That's fair, our native egress pricing is higher. We've chosen to partner with folks like CloudFlare for what we call CDN Interconnect ( https://cloud.google.com/interconnect/cdn-interconnect ) although this was a somewhat recent announcement. As far as GCS pricing goes (rather than egress), I think we've been more cautious on the "cost per op" but really led again on cost per byte. This was especially true when we l…

CDN interconnect is just a bonus :). I prefer GCS having competitive pricing and features since it will be one fewer service to manage.

Also cloudflare is a bit confusing. We only want to serve assets and we serve 3TB per month and I'm not sure if cloudflare is OK with that usage in its free tier option.

Post reply on HN