Earlier quoted context omitted.
You could have done the same on AWS (source: I have worked at AWS for 6 years, and know GCP very well)
AWS doesn't have AppEngine or the Datastore. Yes, there is similar products, but they are absolutely not 'the same'.
Spotify moves its back end to Google Cloud
281–290 of 397 posts
Re: Spotify moves its back end to Google Cloud
#282Earlier 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.
You can quite comfortably live on $35k a year after rent, if you're a single person supporting just yourself. I managed to spend 3 years at university living on less than that. I've just spent the last 3 months interning for NZ$20 an hour (~$40k a year), much of that was spent paying about $260 a week for rent (paying rent for 2 places due to contracts). I managed to get along just fine. Cost of living-wise, where I…
Re: Spotify moves its back end to Google Cloud
#283Earlier quoted context omitted.
The main reason I tend to shy away from GC is that it's blocked in China. AWS isn't (which also means Heroku isn't blocked since Heroku runs on AWS, so I use AWS for IaaS and Heroku for PaaS). If you plan to offer multi-lingual content, anticipate having viewers in that part of the world, and your content isn't something they would be interested in blocking, it's just a practicality worth factoring in. Another reason…
The old App Engine / API / Admin console era is over. All tasks have been migrated to https://console.cloud.google.com/ including some of the last App Engine specific administration things.
My pet peeve with cloud services and their web-based admin GUIs is that you have to use the GUI or the APIs to do anything. You can't capture the current configuration and then replay it if anything is misconfigured. You can't save or restore the config. You can't diff the config across versions. Most SaaSes don't even have audit logs, or if they do, they're too minimalistic to provide the ability to get a lot of detail or roll back anything.
My wish list item is a kind of "Puppet for GCE". I write my manifest, push them to the cloud, and stuff happens. If something isn't mentioned in my manifest, it gets deleted. Truthfully, I don't want to use a web GUI at all.
At the very least there should be a way to do an inventory of an account. Recently I needed to take over an older AWS account, and I wanted to find out what was in it — instances, load balancers, buckets, and so on. It's virtually impossible to do this with the management console since the ontology of possibly configurable objects is so huge and complicated, and pretty much everything has a computer-generated hash instead of a human name, so I was surprised when I couldn't find anything.
Re: Spotify moves its back end to Google Cloud
#284Earlier quoted context omitted.
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 :)
Re: Spotify moves its back end to Google Cloud
#285Earlier quoted context omitted.
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 ba…
I also want to understand the cost doffs as a Well.
Re: Spotify moves its back end to Google Cloud
#286Congrats 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.
Re: Spotify moves its back end to Google Cloud
#287Earlier quoted context omitted.
I've been relying on multiple Cloud offerings (including PaaS, IaaS etc) outside Google for many years, but for some unclear reason, I cannot manage to consider Google a reliable partner for a type of hosting or another, at this point. I would love to be proven wrong really, because I often look at their GC offering, and I /really/ want to dive in, yet I feel that I would risk having to migrate quickly in 2 weeks at…
I have been running my website on AppEngine for 6+ years now. No problems at all.
cloud.google.com/appengine/docs/
and let me know what you think? This is an iterative effort of course, so more changes to come. Thanks again!
Re: Spotify moves its back end to Google Cloud
#288Earlier quoted context omitted.
They'd be buying the users.
That's about the only real value. But then what? Do they run the two entities separately? Or merge Google's offering with Spotify and risk pissing customers off who are loyal to the Spotify brand and app?
Re: Spotify moves its back end to Google Cloud
#289At 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…
Disclaimer: I work in Cloud Support.
Re: Spotify moves its back end to Google Cloud
#290I 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.
Hi pdknsk, I'm a Product Manager on App Engine and wanted to reach out and say that 100% we are invested in app engine and are working to make it your favorite platform. For example, we heard that GAE documentation needs enhancements and we've kicked off a large project to do just this. It's an ongoing effort as you can imagine, but please take a look at the new landing page and managed VM content as well as the left…
As of 2016, AWS is the better bet.