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

311–320 of 397 posts

Re: Spotify moves its back end to Google Cloud

#311

Post by skybrian »

developer2 wrote: post #264
ASinclair wrote: post #138

Earlier quoted context omitted.

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.

Most adults do not consider having a "room in a shared apartment" to be adequate. A living wage allows you to rent/mortgage a place of your own. What I'm hearing is that $50k is not a living wage.

You're out of touch. It might not be common for families, but it's very common for young adults to share an apartment. And you're trivializing what activists are trying to do when they talk about making sure people have a "living wage."

Re: Spotify moves its back end to Google Cloud

#312

Post by dlgeek »

snowwrestler wrote: post #294
abrookewood wrote: post #182

Earlier quoted context omitted.

The problem (I suffer from it as well), is that people naturally feel that the corporate offerings from Google will mirror the experience that they have with the consumer offerings from Google. And the big issue with Google's consumer offerings is that they seem to have limited to no support and that there is a very real chance that Google will just shut them down all of a sudden. This is the exact opposite of what y…

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 post to our service's forums and indicate issues.

Re: Spotify moves its back end to Google Cloud

#313

Post by skybrian »

Scarbutt wrote: post #281
latchkey wrote: post #142

Earlier quoted context omitted.

AWS doesn't have AppEngine or the Datastore. Yes, there is similar products, but they are absolutely not 'the same'.

Is datastore tied to appengine? some parts of the docs say "datastore is for appengine" and other parts don't mention appengine at all.

It used to be but not anymore; you can use it separately now.

Re: Spotify moves its back end to Google Cloud

#314

Post by dantiberian »

simonebrunozzi wrote: post #71

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

I've made feedback on AWS docs, and every time I get a followup from the person responsible for that documentation (different section each time).

Re: Spotify moves its back end to Google Cloud

#316

Post by Dr_tldr »

nkw wrote: post #203
kbenson wrote: post #185

Earlier quoted context omitted.

> Disclaimer: IAMALBIANYL. I like that one. :) I have a question though, is the prevalence of taglines in any way related to legal requirements? Do you have to stipulate that you aren't a lawyer when stating things because otherwise people to construe it as legal advice, or is it just a fun little identifier of how valid we should consider information to be (like it is in other acronyms of the same type)?

I think it may stem from laws and rules related to practicing law, but there is certainly not any "requirement" to stipulate you are not a lawyer when speaking about legal things. However there are a few things to be mindful of: In the (all of the) United States (and many other countries) the profession of lawyer or attorney is regulated and requires a license to practice as such. In many places to practice law witho…

It may have started as an ass-covering move, but I also think of it as a common courtesy for letting people know that you're offering non-specialist advice and to take it with a grain of salt.

I kind of wish people did that for more things: "I am not theologian/windows user/empathetic person, but..."

Re: Spotify moves its back end to Google Cloud

#317

Post by stevenleeg »

waffle_ss wrote: post #104
stevenleeg wrote: post #40

Earlier quoted context omitted.

Got it, thanks! What about running a postgres container on GKE?

Lots of reasons not to. You'd be in charge of setting up backups (e.g. setting up WAL-E + an S3 bucket and monitoring that - and you'd have to add WAL-E support to your Docker image, which is a PITA), have to perform database upgrades yourself, have to monitor resource usage (CPU, memory, and disk), have to worry about how to manage the Docker volume so that write performance doesn't suffer (Docker defaults to copy-o…

Ahh totally makes sense. Thanks a ton for the insight, it's super helpful!

Re: Spotify moves its back end to Google Cloud

#318

Post by jpatokal »

jhgg wrote: post #292
jpatokal wrote: post #289

Earlier quoted context omitted.

Billing support is provided for free to all customers. If you had trouble with a particular ticket, please feel free to ping me. Disclaimer: I work in Cloud Support.

Thanks for the reply! I don't remember the specific issue, but we had a billing inquiry and were told we had to upgrade to a paid support plan to get an answer.

Please feel free to forward the ticket to me at jani at google, and I'll look into it.

Re: Spotify moves its back end to Google Cloud

#319

Post by zbjornson »

jhgg wrote: post #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…

GCP has locally attached SSDs on almost all machine types and up to 64 TiB of block storage, configurable. What features were you missing?

Re: Spotify moves its back end to Google Cloud

#320

Post by jdubs »

obulpathi wrote: post #67
liveoneggs wrote: post #42

Earlier quoted context omitted.

> infinitely auto-scalable platform where we don't have to do any devops or carry a pager You never know what you don't measure and test

One of the big advantages of Google Cloud platform is "Scalability". Load balancers: Scale to millions of users seamlessly. No warming up, no tickets, ... PubSub: You can send the whole Internet 10 times in a day through it. Google does that every day Big Query: Its equivalent to spinning up a 100+ node cluster in a matter of seconds and it can process data at speeds of GB's of data per sec, I heard couple of use cas…

Sounds expensive when no one is looking at how the magic works.
Post reply on HN