Labels
Amazon Web Services
Android
APIs
Business Services
code
Comcast
Disaster Recovery
domains
Drivers
e-commerce
Email
Engineering
enom
Fail
Fraud
Gentoo
Google
Google Apps
Internet
iPhone
Linux
Mac
Microsoft
Mobile Workforce
Phone Solicitation
PHP
PostgreSQL
Remote Support
Security
SEO
Video
VoIP
Web-Applications
WebEx
Windows
Blog Archive
- May 2012 (1)
- April 2012 (1)
- March 2012 (2)
- February 2012 (1)
- January 2012 (1)
- December 2011 (2)
- November 2011 (2)
- September 2011 (2)
- August 2011 (1)
- July 2011 (1)
- June 2011 (4)
- May 2011 (2)
- April 2011 (1)
- March 2011 (1)
- February 2011 (1)
- December 2010 (1)
- November 2010 (1)
- August 2010 (2)
- July 2010 (4)
- June 2010 (1)
- May 2010 (1)
- March 2010 (2)
- February 2010 (1)
- January 2010 (1)
- December 2009 (1)
- November 2009 (1)
- October 2009 (2)
- August 2009 (1)
- July 2009 (4)
- June 2009 (4)
- May 2009 (1)
- April 2009 (4)
- March 2009 (1)
- February 2009 (1)
- January 2009 (5)
- December 2008 (1)
- November 2008 (3)
- October 2008 (4)
- September 2008 (10)
- August 2008 (6)
Thursday, September 25, 2008
New Content Delivery Network
We all know that one of the top guidelines from YSlow is to implement a CDN when possible. We just implemented this for all of our sites! We then ran some simulated traffic tests against our site. What an improvement! We already had high marks from YSlow on our site this was one of the last steps needed to get almost all As from YSlow.
Bottom line - Content Distribution Networks are super easy to implement and offer a significant performance improvements for any web-site.
A cheap way of doing CDN is to simply host two sites on the same server, the primary site and cdn.example.com. This will load-distribute the content and increase the responsiveness of the site. Hopefully the server used has enough resources to handle the traffic load. A better option is to use a secondary server. Amazon Web Services is also introducing a CDN system soon.
Subscribe to:
Post Comments (Atom)

0 comments:
Post a Comment