Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Google has quietly launched a CDN

venturebeat.com

Post reply on HN
Print view View original

11–20 of 46 posts

Re: Google has quietly launched a CDN

#11

Post by dorfsmay »

hayksaakian wrote: post #8
dorfsmay wrote: post #6

Earlier quoted context omitted.

Usually you created CNAMEs from your domain to your CDN's.

Is it best practice to use a separate domain for CDN because of cookies? Eg: examplecdn.com instead of cdn.example.com

If you trust your CDN, then no, you have less issues if you use the same domain as the one you use for your APIs.

Re: Google has quietly launched a CDN

#12

Post by c0nducktr »

cagenut wrote: post #4

Not to rag on the offering, but the headline is just not right. This is a CloudFront competitor not an Akamai competitor. Its a very rigid barebones product at a low margin via self-serv tooling.

If we're discussing headlines, can "has quietly X" stop already?

Re: Google has quietly launched a CDN

#15

Post by nickbauman »

cagenut wrote: post #4

Not to rag on the offering, but the headline is just not right. This is a CloudFront competitor not an Akamai competitor. Its a very rigid barebones product at a low margin via self-serv tooling.

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.

Re: Google has quietly launched a CDN

#17

Post by jdub »

mkj wrote: post #7
cagenut wrote: post #4

Not to rag on the offering, but the headline is just not right. This is a CloudFront competitor not an Akamai competitor. Its a very rigid barebones product at a low margin via self-serv tooling.

Google's reach of "Edge Caches" seems closer to Akamai's than CloudFront's though - lots of indivdual ISPs have them.

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.

Re: Google has quietly launched a CDN

#18

Post by valverde »

dorfsmay wrote: post #11
hayksaakian wrote: post #8

Earlier quoted context omitted.

Is it best practice to use a separate domain for CDN because of cookies? Eg: examplecdn.com instead of cdn.example.com

If you trust your CDN, then no, you have less issues if you use the same domain as the one you use for your APIs.

It's not about the security of the cookies, it's about the bandwidth you save by having a separate domain for static content, because the client does not have to transmit the cookies for each request.

Re: Google has quietly launched a CDN

#19

Post by rybosome »

dorfsmay wrote: post #11
hayksaakian wrote: post #8

Earlier quoted context omitted.

Is it best practice to use a separate domain for CDN because of cookies? Eg: examplecdn.com instead of cdn.example.com

If you trust your CDN, then no, you have less issues if you use the same domain as the one you use for your APIs.

You should host user content (specifically JavaScript files) on a separate domain though, otherwise you put user cookies at risk.
Post reply on HN