=46irst we made a DNS CNAME entry = for a sub domain of our website domain
images.ourdomain.com pointing to
c3oxxac8nfudd5= .cloudfront.netThen we did a find and replace on the whole= site so that all images are served via the images.ourdomain.com subdomai= n
So now page requests come to our server and are processed by Web= DNA as normal but images are called via images.ourdomain.com which p= oints to Cloud=46ront. Cloud=46ront serves the file if it has it but= if not it pulls it from our server and caches it for the next request.
So now very few image files are served from our a= ctual server. Our bandwidth usage and server load both dropped drama= tically. There was the added benefit of the images being served from a bi= gger and better server closer to the customer so the whole page loads muc= h faster for users.
Paul
On 20= Jul 2011, at 01:53, Alex McCombie <
info=40adventureskies.com> wrote:
Hey everyone,
Basically I am trying to cost= out a redundant setup for what I have
here.
Moderate DNA traffic a= nd I am looking to figure out a cost effective way to
either off-site = some DNA sites or serve the DNA from my servers and just
call images f= rom a provider with a bigger pipe.
I am inclined to start with the= image serving route. That means that I don't
necessarily need someone= with a DNA server, but If the pricing is right then
I might be inclin= ed to move a few sites to a full DNA host.
This will NOT be used f= or big files. No videos, no zip files, etc. This is
strictly for webpa= ge imagery and some javascripts (for menus and the like).
I just n= eed a reliable provider with 99.9 uptime and a commercial pipe.
Pl= ease contact me off-list if you think you can help.
Thanks
Alex
=
Alex=40Adventureskie= s.com--
Alex J. McCombie
---------------------------------------------------------=
This message is sent to you because you are subscribed to
the mail= ing list <talk=40webdna.us= >.
To unsubscribe, E-mail to: <talk-leave=40webdna.us>
archives: http://mail.webdna.us/list/ta= lk=40webdna.us
Bug Reporting: support=40webdna.us
= --Boundary_(ID_2X2f8qxY0wkVJTWXjSgnCA)--
Associated Messages, from the most recent to the oldest:
--Boundary_(ID_2X2f8qxY0wkVJTWXjSgnCA) Content-type: text/plain; CHARSET=US-ASCII Content-transfer-encoding: 7BIT Content-disposition: inline A quick and easy way to offload the images is using Amazon CloudFront
. It's a CDN that can use any server as its source We started with a fairly image heavy WebDNA site. We signed up to Amazon Web Services and created a CloudFront pointing to our server (a few clicks in the AWS admin console). That gives you a random domain name like c3oxxac8nfudd5.cloudfront.net First we made a DNS CNAME entry for a sub domain of our website domain images.ourdomain.com (http://images.ourdomain.com) pointing to c3oxxac8nfudd5.cloudfront.net Then we did a find and replace on the whole site so that all images are served via the images.ourdomain.com subdomain So now page requests come to our server and are processed by WebDNA as normal but images are called via images.ourdomain.com which points to CloudFront. CloudFront serves the file if it has it but if not it pulls it from our server and caches it for the next request. So now very few image files are served from our actual server. Our bandwidth usage and server load both dropped dramatically. There was the added benefit of the images being served from a bigger and better server closer to the customer so the whole page loads much faster for users. Paul On 20 Jul 2011, at 01:53, Alex McCombie
wrote: > Hey everyone, > Basically I am trying to cost out a redundant setup for what I have > here. > Moderate DNA traffic and I am looking to figure out a cost effective way to > either off-site some DNA sites or serve the DNA from my servers and just > call images from a provider with a bigger pipe. > > I am inclined to start with the image serving route. That means that I don't > necessarily need someone with a DNA server, but If the pricing is right then > I might be inclined to move a few sites to a full DNA host. > > This will NOT be used for big files. No videos, no zip files, etc. This is > strictly for webpage imagery and some javascripts (for menus and the like). > > I just need a reliable provider with 99.9 uptime and a commercial pipe. > > Please contact me off-list if you think you can help. > Thanks > Alex > > Alex@Adventureskies.com (mailto:Alex@Adventureskies.com) > > > > > -- > Alex J. McCombie > > . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . > > Adventure Skies Interactive > > 479 County Route 35 Fulton, NY 13069 > > p. 315 .402 .6377 > > e. Alex@AdventureSkies.com (mailto:Alex@AdventureSkies.com) > > www.AdventureSkies.com (http://www.AdventureSkies.com) > > > > --------------------------------------------------------- > This message is sent to you because you are subscribed to > the mailing list . > To unsubscribe, E-mail to: > archives: http://mail.webdna.us/list/talk@webdna.us > Bug Reporting: support@webdna.us (mailto:support@webdna.us) --Boundary_(ID_2X2f8qxY0wkVJTWXjSgnCA) Content-type: text/html; CHARSET=US-ASCII Content-transfer-encoding: quoted-printable Content-disposition: inline
We started with a fairly image heavy WebDNA site. = We signed up to Amazon Web Services and created a Cloud=46ront pointing t= o our server (a few clicks in the AWS admin console). That gives you a ra= ndom domain name like c3oxxac8nfudd5.cloudfront.net