Spotify moves its back end to Google Cloud

Re:Spotify moves its back end to Google Cloud by boulos on Wednesday February 24, 2016 @01:39AM (#11164980)

That's fair, our native egress pricing is higher. We've chosen to partner with folks like CloudFlare for what we call CDN Interconnect (https://cloud.google.com/interconnect/cdn-interconnect) although this was a somewhat recent announcement.

As far as GCS pricing goes (rather than egress), I think we've been more cautious on the "cost per op" but really led again on cost per byte. This was especially true when we launched Nearline, triggering AWS to launch S3-IA (but with lots of caveats like small files and still a 25% higher base rate).

While not integrated directly into GCS / GCP, does going through CloudFlare alleviate some of your concern?

[ Parent | on HN ]

Re:Spotify moves its back end to Google Cloud by boundlessdreamz on Wednesday February 24, 2016 @04:06AM (#11165451)

CDN interconnect is just a bonus :). I prefer GCS having competitive pricing and features since it will be one fewer service to manage.

Also cloudflare is a bit confusing. We only want to serve assets and we serve 3TB per month and I'm not sure if cloudflare is OK with that usage in its free tier option.

[ Parent | on HN ]

Re:Spotify moves its back end to Google Cloud by boulos on Wednesday February 24, 2016 @01:47PM (#11169099)

I think CloudFlare, Fastly, et al. are all happy to have you serve 3 TiB per month. Their hope is that you grow and upgrade to their paid plans one day.

[ Parent | on HN ]