Google has quietly launched a CDN • Hacker News Board

Re: Google has quietly launched a CDN

#41

Post by nickbauman » Mon, Dec 14, 2015, 6:45 PM UTC

alooPotato wrote: post #28

nickbauman wrote: post #15

Earlier quoted context omitted.

The best part about it, I automatically write to three caches whenever I write to GAE datastore. One to the instance, one to memcache and one to Google's edge cache. It's just part of the GAE api, you get it for free.

Do you have a link that support your third assertion? How does writing to the GAE datastore also put the entity into the edge cache?

OK, I'm actually wrong here. You still have to write headers to get it to go into the edge cache. So from the Python API for webapp2:

  self.response.cache_control = 'public'
  self.response.cache_control.max_age = 300

Does the trick

Re: Google has quietly launched a CDN

#42

Post by wernerb » Mon, Dec 14, 2015, 10:31 PM UTC

tszming wrote: post #37

wernerb wrote: post #33

Earlier quoted context omitted.

Cloudfront is not available in China. We had to implement a small CDN for a large ecommerce website. What we did was use geo-ip route 53 and route chinese ips to load balanced nginx instances caching the cloudfront cdn. What compounds the problem with China is that the chinese are very much used to requesting an english language variant of the webstore as its often cheaper. This circumvents the CDN however as all sta…

I've a few instances in aliyun (alibaba cloud) to monitor the traffic from time to time, Cloudfront works for me now, while googleapis.com is blocked. I cannot convince myself not to use a politically neutral company (or China friendly) like AWS, Azure.. when I am considering the CDN service.

Oh yeah its accessable from China. But I meant that there is no cloudfront edge region in China so chinese customers must cross the firewall and it is really really slow for them.

Re: Google has quietly launched a CDN

#43

Post by jdub » Tue, Dec 15, 2015, 1:00 AM UTC

brazzledazzle wrote: post #40

jdub wrote: post #17

Earlier quoted context omitted.

I have pretty strong doubts that the Google Cloud Platform team would have convinced the broader organisation to host customer stuff on their mission critical caches. As I understand it, there's not a lot of dogfooding (let alone cooperation!) between GCP and Google.

A small counterpoint: I saw a talk recently that discussed charging other Google teams for using GCP resources to discourage wastefulness.

My understanding is the accounting for services process happened prior to GCP, and isn't about GCP resources.

Re: Google has quietly launched a CDN

#44

Post by brazzledazzle » Wed, Dec 16, 2015, 4:18 PM UTC

jdub wrote: post #43

brazzledazzle wrote: post #40

Earlier quoted context omitted.

A small counterpoint: I saw a talk recently that discussed charging other Google teams for using GCP resources to discourage wastefulness.

My understanding is the accounting for services process happened prior to GCP, and isn't about GCP resources.

The talk specifically discussed GCP being free for internal use and one of it's costlier services being used without any thought being put toward optimization. Once they started charging they optimized and used dramatically less.

Re: Google has quietly launched a CDN

#45

Post by alooPotato » Sat, Dec 19, 2015, 3:50 PM UTC

nickbauman wrote: post #41

alooPotato wrote: post #28

Earlier quoted context omitted.

Do you have a link that support your third assertion? How does writing to the GAE datastore also put the entity into the edge cache?

OK, I'm actually wrong here. You still have to write headers to get it to go into the edge cache. So from the Python API for webapp2: self.response.cache_control = 'public' self.response.cache_control.max_age = 300 Does the trick

That just sets the responses cache control headers. It doesn't put anything in the edge cache

Re: Google has quietly launched a CDN

#46

Post by nickbauman » Mon, Dec 21, 2015, 8:20 PM UTC

alooPotato wrote: post #45

nickbauman wrote: post #41

Earlier quoted context omitted.

OK, I'm actually wrong here. You still have to write headers to get it to go into the edge cache. So from the Python API for webapp2: self.response.cache_control = 'public' self.response.cache_control.max_age = 300 Does the trick

That just sets the responses cache control headers. It doesn't put anything in the edge cache

... the headers trigger storing into the edge cache.