Hi Everyone.
There are few modules, which help to serve Drupal website using CDN with Origin Pull or Push Technologies.
However, i don't want to do the things they do. They are most of the times, helping to keep the files or rich media on their cached servers, which can be used from Points of Presence of CDN provider. If we host files with them and use some URL, the files may end up hosted on some subdomain like cdn.site.com (which i don't think is good)
I want that the site page is cached on their server's POP and then, refreshed from our side (even drupal can send a command to POP, in case we have updated page) Or there is specific time, when they cache the content again (to get the fresh content).
Is something like this possible ?
Regards
Dhaliwal
Comments
Big Bucks
If you got the money I know Akamai will do HTML CDN
http://drupal.org/project/akamai
Akamai wants to rip people
Akamai wants to rip people and i guess only big corporations can afford them.
NetDNA is better in terms of pricing.
Amazon just started offering
Amazon just started offering this:
Host Your Static Website on Amazon S3
http://aws.typepad.com/aws/2011/02/host-your-static-website-on-amazon-s3...
Cool
Saw that as well. Got me thinking I should make the 7.x version of boost support a sub module that would create friendly S3 file names and allow for rewriting of the links to point to .html versions of a page. In short integrate with one of these.
http://drupal.org/project/html_export
http://drupal.org/project/savetoftp
Storage API might be even
Storage API might be even better for this - see http://drupal.org/project/storage_api and in there esp. "Amazon S3 / CloudFront - files are uploaded to an S3 'bucket'. Serving is handled by S3 or CloudFront. Also supports media streaming and time-limited cryptographically-signed URLs."
---
Tomáš J. Fülöpp
http://twitter.com/vacilandois
Any progress in adapting
Any progress in adapting Boost to serve HTML pages from the WWW server on AWS S3?
---
Tomáš J. Fülöpp
http://twitter.com/vacilandois
Options
First, having your asset files on subdomains can be a good idea:
http://developer.yahoo.com/performance/rules.html
Under "Reduce DNS Lookups":
"Reducing the number of unique hostnames has the potential to reduce the amount of parallel downloading that takes place in the page. Avoiding DNS lookups cuts response times, but reducing parallel downloads may increase response times. My guideline is to split these components across at least two but no more than four hostnames. This results in a good compromise between reducing DNS lookups and allowing a high degree of parallel downloads."
I.e., it may bring performance benefits to CNAME several subdomains (images.mydomain.com, video.mydomain.com, etc.) to your own, and have all of these delivered via CDN. I've worked on projects where different subdomains are delivered by different CDNs, each offering different performance-versus-cost value.
See also http://drupal.org/project/parallel
Most people agree that Akamai is the top of the line service. A significantly less expensive service that works in the same way is CDNetworks:
http://www.us.cdnetworks.com/
Both services offer a cache management API. The Akamai module that mikeytown2 linked to works pretty well; there's no module specifically for the service, but you may get value out of the more advanced
http://drupal.org/project/cdn
Why having content on sub-domain a bad idea !
I have extensively tested this on my site and delivering images from my CDN cache sub-domain seems to have negative effect on "Google Image" traffic on my site, I think since Google makes use of domain authority to decide page ranking the same should be applicable for image search and since our NEW cdn-subdomain does not have that results in a negative way.