I see more and more sites that create vhosts and host files on static.theirdomainname.com. What’s up with this? Why is this a pattern I’ve seen?
I see more and more sites that create vhosts and host files on static.theirdomainname.com.
Share
Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I see more and more sites that create vhosts and host files on static.theirdomainname.com. What’s up with this? Why is this a pattern I’ve seen?
Sometimes companies will pay a 3rd party company to host their static content (images, stylesheets, video, etc) on something called a Content Delivery Network (CDN), which has nodes (aka servers) all around the globe. They’ll keep copies of your content on all those nodes, so that when people visit your site, the content will be delivered quickly, from the node closest to them. You create a sub-domain (like static.domainname.com) and point it at the CDN’s DNS, then they take care of forwarding requests for your static content to the perfect node. Some popular CDNs include Akamai, Amazon CloudFront, and Nirvanix.