[1] https://code.google.com/p/google-compute-engine/issues/detai... [2] https://code.google.com/p/google-compute-engine/issues/detai... [3] https://code.google.com/p/google-compute-engine/issues/detai... [4] https://code.google.com/p/google-compute-engine/issues/list
Spotify moves its back end to Google Cloud
261–270 of 397 posts
Re: Spotify moves its back end to Google Cloud
#262Earlier quoted context omitted.
AppEngine is Google Cloud Platform's PaaS offering. Its the oldest product on Google Cloud Platform, but its not one of the ones mentioned that Spotify is using (the Spotify post doesn't talk much about the products, but Google's [0] does.) The Google Cloud Platform services they are identified as using are: Cloud Storage, Compute Engine, Cloud Datastore, Cloud Bigtable, Direct Peering, Cloud VPN, Cloud Router, Cloud…
I guess they are not entirely on Google Cloud but rather their data warehousing / big data stuff is now?/going? to be on GCP. I don't really call big data processing "backend" but rather the microservices the backend. Its not clear to me if those are going to be ported over or if they are already. Does spotify plan on porting everything over or just the heavy computing? A detailed techy case study I hope will follow…
I don't know why you would guess that: the Google announcement indicates that the migration has both a "services" track and a "data" track. And Spotify's announcement certainly seems to indicate that they are moving off of their own datacenters, onto Google Cloud Platform, and not in a limited way.
Re: Spotify moves its back end to Google Cloud
#263Earlier quoted context omitted.
I want to see your lovely face in the office every day. =)
Man, you should consider remote options at least for the Customer Success given how low you're paying (is $50K really livable in San Francisco?).
If it's truly prohibitive for a single person to live in SF for $50K per year then we should be really concerned about the families that earn $50K from two minimum wage jobs, and need to support 1 to 2 children on top of it.
Re: Spotify moves its back end to Google Cloud
#264Earlier quoted context omitted.
...and I'm assuming you've got some killer rent control, or some other non-scalable, non-replicable housing situation. That's neat for you, but it's meaningless to anybody else.
I signed the lease in the past two years. So rent control has kicked in once. I have a room in a shared apartment. There are plenty of open rooms on Craigslist for similar rents. I'm not saying life will be great but it's entirely possible to live in the city on $50k/yr.
Re: Spotify moves its back end to Google Cloud
#265Does Google Cloud offer an equivalent to AWS Direct Connect?
Re: Spotify moves its back end to Google Cloud
#266I want to commend some of the Google Compute Platform employees that commented in this thread. I was at AWS for 6 years (left 2 years ago... today!), and I've always been a proponent of being more open and communicative with developers, but it rarely happened - I guess that AWS' PR policy and such are a big showstopper for these kind of discussions. Although, some individuals did their best (e.g. Jeff Barr) to try to…
The Google Cloud guys are always all over Hacker News threads whenever it comes up. I wish they had the same exuberance about their support tickets :(
Is there a particular ticket (or tickets) you ran into trouble with? I can try to follow up.
Re: Spotify moves its back end to Google Cloud
#267I have some questions based on previous experience many moons ago experience (3 or 4 yrs). When I tried to port some of our platform to AppEngine I had some issues with various Java libraries (writing tmp files, opening sockets, etc). Once I sort of got past that and used some of Googles own APIs (which is sort of annoying that I had to couple my stuff) I had timeout issues. See we have to integrate with all these en…
If you're looking for "just run my app" but with a bit more customization / flexibility than App Engine (like running your own RabbitMQ) then yes, Container Engine (https://cloud.google.com/container-engine) is our hosted Kubernetes offering. You don't need to manage with the VMs yourself, just choose a cluster size and go.
Disclaimer: I work on Compute Engine, not really App Engine or Container Engine (but I'm familiar with them all).
Re: Spotify moves its back end to Google Cloud
#268I notice App Engine isn't mentioned in their stack. I'm a bit worried that Google abandons it once Snapchat moves off it. It has already been in maintenance mode for some years now (save for Managed VMs). The writing was on the wall when Guido left the team. Apparently Google still uses it internally (as the recent switch to Monorail made evident), so perhaps it's safe for a few more years.
Re: Spotify moves its back end to Google Cloud
#269Earlier quoted context omitted.
I want to see your lovely face in the office every day. =)
Man, you should consider remote options at least for the Customer Success given how low you're paying (is $50K really livable in San Francisco?).
Re: Spotify moves its back end to Google Cloud
#270Earlier quoted context omitted.
I guess they are not entirely on Google Cloud but rather their data warehousing / big data stuff is now?/going? to be on GCP. I don't really call big data processing "backend" but rather the microservices the backend. Its not clear to me if those are going to be ported over or if they are already. Does spotify plan on porting everything over or just the heavy computing? A detailed techy case study I hope will follow…
> I guess they are not entirely on Google Cloud but rather their data warehousing / big data stuff is now?/going? to be on GCP. I don't know why you would guess that: the Google announcement indicates that the migration has both a "services" track and a "data" track. And Spotify's announcement certainly seems to indicate that they are moving off of their own datacenters, onto Google Cloud Platform, and not in a limit…