News for hackers. Stuff that matters.

A comment on Spotify moves its back end to Google Cloud. Parent comment

Re:Spotify moves its back end to Google Cloud by Hermel on Tuesday February 23, 2016 @03:49PM (#11162205)
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).

[ Parent | on HN ]
Re:Spotify moves its back end to Google Cloud by boulos on Tuesday February 23, 2016 @03:56PM (#11162261)
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.

[ Parent | on HN ]
Re:Spotify moves its back end to Google Cloud by plexicle on Wednesday February 24, 2016 @12:29AM (#11164750)
I love GCE. I really would like to see Node on it natively, without the need for ManagedVM. I tried it a while ago and did not want to deal with all of the Docker stuff. It was especially a pain on Windows. :(
[ Parent | on HN ]
Re:Spotify moves its back end to Google Cloud by kiennt on Tuesday February 23, 2016 @08:36PM (#11163864)
Managed VM is still beta, I think only brave one could try beta for production.
[ Parent | on HN ]
Re:Spotify moves its back end to Google Cloud by mvitorino on Wednesday February 24, 2016 @06:37AM (#11165968)
We have been using Managed VMs in production for while now, integrated in a micro-services architecture, for non-essential, non-frontend services and are quite happy with it. Using custom VMs (Docker based) and work like a breeze.
[ Parent | on HN ]
Re:Spotify moves its back end to Google Cloud by stickfigure on Tuesday February 23, 2016 @04:17PM (#11162403)
Traditional App Engine is not particularly cost-effective for compute-intensive loads, but it works great for basic web workloads. If you have special needs, Managed VMs have the performance characteristics of the underlying Compute Engine node. We've found that App Engine is not "all or nothing"; it's the backbone of our app but we run services where they make the most sense (usually GCE).
[ Parent | on HN ]
Re:Spotify moves its back end to Google Cloud by vgt on Tuesday February 23, 2016 @04:33PM (#11162519)
In addition to all the excellent comments here. Let's not forget that the massive massive Snapchat runs almost entirely on Google AppEngine. So if AppEngine can handle their scale, it can handle most others :)
[ Parent | on HN ]
Re:Spotify moves its back end to Google Cloud by iampims on Tuesday February 23, 2016 @05:10PM (#11162763)
No longer true. It's all GCE now last I heard.
[ Parent | on HN ]
Re:Spotify moves its back end to Google Cloud by vgt on Tuesday February 23, 2016 @05:36PM (#11162918)
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).

[ Parent | on HN ]
Re:Spotify moves its back end to Google Cloud by arouzrokh on Tuesday February 23, 2016 @08:13PM (#11163737)
+1

App Engine Product Manager here

[ Parent | on HN ]
Re:Spotify moves its back end to Google Cloud by ariwilson on Tuesday February 23, 2016 @04:08PM (#11162347)
Default AppEngine instance is only running at 600MHz. You can choose to pay for a faster instance:

https://cloud.google.com/appengine/docs/python/modules/#Pyth...

[ Parent | on HN ]
Re:Spotify moves its back end to Google Cloud by obulpathi on Tuesday February 23, 2016 @03:53PM (#11162238)
App Engine expects your web apps to return almost immediately (in a matter of few ms). For anything that takes longer, you need to use task queues in App Engine. Or maybe try AppEngine Managed VM's?
[ Parent | on HN ]
Re:Spotify moves its back end to Google Cloud by oaktowner on Tuesday February 23, 2016 @06:40PM (#11163299)
App Engine requests time out after 60 seconds (that's 60000 ms).

https://cloud.google.com/appengine/articles/deadlineexceeded...

(I work at Google, but not on App Engine)

[ Parent | on HN ]
Re:Spotify moves its back end to Google Cloud by colonelxc on Tuesday February 23, 2016 @07:57PM (#11163676)
They don't have to if you use Basic or Manual Scaling (Then they can run up to 24 hours).

https://cloud.google.com/appengine/docs/java/modules/#Java_I...

If you run multiple modules at once (some serving the frontend, some for longer tasks w/task queues), you can have the best of both worlds and use different scaling options for each.

(I also work at Google, but also not on App Engine)

[ Parent | on HN ]