Live data from Hacker News

Spotify moves its back end to Google Cloud

news.spotify.com

271–280 of 397 posts

Re: Spotify moves its back end to Google Cloud

#271
post #180

Earlier quoted context omitted.

No longer true. It's all GCE now last I heard.

Where'd you hear that? Not without risk of giving an argument from authority, your sources are inaccurate. As late as November of last year Snapchat was on stage talking about their broad AppEngine use. (I work on Google Cloud).

+1

App Engine Product Manager here

Re: Spotify moves its back end to Google Cloud

#272
post #180

Earlier quoted context omitted.

No longer true. It's all GCE now last I heard.

Where'd you hear that? Not without risk of giving an argument from authority, your sources are inaccurate. As late as November of last year Snapchat was on stage talking about their broad AppEngine use. (I work on Google Cloud).

[deleted]

Re: Spotify moves its back end to Google Cloud

#273
post #136
post #108

Earlier quoted context omitted.

Look no further (for item 1 of 2 anyway) — http://googlecloudplatform.blogspot.co.nz/2015/12/the-next-g...

Can't emphasize enough how much I wish GCE had PostgreSQL support. Managing and maintaining our database is something I'd love to hand off to my cloud provider. MySQL simply doesn't cut it these days, and RDS has made me happy and lazy.

can't agree enough. MySQL's quirks make me want to gouge my brain, and it's not going to solidify into a competitive db engine any Time soon. Let's say mariadb added something like hstore--would I ever get that patch?

Re: Spotify moves its back end to Google Cloud

#274

Earlier quoted context omitted.

You can't afford rent in San Francisco at $50,000 a year, period. The going rate for a single bedroom (usually with no tenant's rights) is somewhere around $1,200 a month, well over 30% of your monthly take-home at $50,000/year. If you're going to force people to move to the Bay Area to work for you, you need to pay them enough to afford it. Good luck hiring though.

just playing devil's advocate here but since when do you NEED to spend less than 30% of your take home on rent to survive? There are people out there paying 50% or more of their take home on their rent/mortgage I imagine - it's just not really considered to be wise move in most cases. 1200/mo for a 1 bed doesn't even sound that bad for what's supposed to be the most expensive city to live in America. I know people in…

That's $1200 for a bed in a shared house, not a 1 bed apartment, which goes for about $3300.

Re: Spotify moves its back end to Google Cloud

#275
At work we moved to GCE at the beginning of this year, from Linode after they were having stability issues over the christmas break. No complaints from us. So far have been very happy with it. We were considering moving to AWS, but to realize the same pricing as GCE we'd have to purchase reserved instances - the sustained usage discounts have been huge for us.

Additional things we liked: - gcs is way more responsive than S3. also, was fairly painless to migrate our S3 buckets to GCS via the web console. - peering with cloudflare lets us save on bandwidth costs! - network load balancer has shown itself to be very reliable and solid for holding open A LOT sustained websocket connections. - http load balancer has shown itself to be very capable of ssl termination & routing (love that we can route /api to our API servers, and the rest to our static servers). additionally, no pre-warming was required. when we did the datacenter switch, it was just 5 mins of downtime. didn't have to worry about pre-warming for our production load like we would have on ELB.

Things we didn't like: - salt-cloud's driver for GCE is still lacking. Can't specify disk size for provisioned storage. Can't specify local SSD storage either. Also parallel provisioning didn't work. Something about PyCrypto not liking the way it forked. Not GCE's fault - billing support non-existent unless you purchase a support plan. - documentation still needs some work.

Re: Spotify moves its back end to Google Cloud

#276

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)…

Your website is just a logo and nothing else, how exactly are you growing. What is your business model?

Re: Spotify moves its back end to Google Cloud

#277

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'm on mobile so this initial response will be short: AWS' core product is AWS. They do a damn fine job of providing this. GC's core is "who knows what" - they do a damn poor job of even making an offering if switch thousands and thousands of servers to - let alone thousands and thousands of man hours. Ironically, Google has massive domain knowledge of how to run infra... Yet clueless how to adopt and support and fos…

> Find me a single ops eng on the market who has done scale in GC?

Every user of appengine, for a start. You need to code to their datastore, but apart from that scaling is practically infinite - and completely invisible. We don't need to configure, provision or even * understand * load balancers or geographically redundant servers.

Concrete examples? The royal wedding website was served from appengine a few years back; I imagine you'd be impressed with how that scaled from nothing to phenomenal traffic loads and back again. And Khan Academy, Snapchat, and now Spotify ought to meet your definition of "done scale".

Re: Spotify moves its back end to Google Cloud

#278
post #83
post #72

Earlier quoted context omitted.

Are you happy with the performance of AppEngine? I have tried it last summer and was quite disappointed. CPU-bound programs that completed in a few seconds on my own computer took about ten times as long on AppEngine despite similar nominal specs (GHz and RAM).

If you like the App Engine model, but want a "full computer worth of horsepower", you might want to consider our "Managed VM" environment built on top of Compute Engine: https://cloud.google.com/appengine/docs/managed-vms/ Disclaimer: I work on Compute Engine.

Managed VM is still beta, I think only brave one could try beta for production.

Re: Spotify moves its back end to Google Cloud

#279
post #276

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)…

Your website is just a logo and nothing else, how exactly are you growing. What is your business model?

GearLaunch provides merchants with software that allows them to build and run online storefronts, and also manages production, logistics and customer service for all products sold. GearLaunch is the only e-commerce software provider to cover the entire value chain, enabling marketers to focus on marketing.

https://angel.co/gearlaunch

Re: Spotify moves its back end to Google Cloud

#280

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'm on mobile so this initial response will be short: AWS' core product is AWS. They do a damn fine job of providing this. GC's core is "who knows what" - they do a damn poor job of even making an offering if switch thousands and thousands of servers to - let alone thousands and thousands of man hours. Ironically, Google has massive domain knowledge of how to run infra... Yet clueless how to adopt and support and fos…

I hope that you see the irony of your argument in this thread :)
Post reply on HN