Introduction.
Latest Web sites and applications often need to provide amount of static content to end users.
This content includes images, style sheets, JavaScript, and video.
The increase in the number of static assets and the increase grows the bandwidth usage increases page load time decreased, depending on the size of the user's search experience, and reduce the usable capacity of the server.
Dramatically improving performance, reducing the page load time reduce the bandwidth and infrastructure costs, you can implement a content delivery network, And CDN cache these assets at a set of servers that are geographically distributed.
What is a CDN?
Content delivery network is a group of servers distributed geographically optimized to provide static content to end users. While this static content can be almost any type of data, CDNs are most commonly used to deliver web pages and related files, streaming video and audio, and large software packages.
A CDN consists of multiple PoPs (Point of Presence) in various locations, and each port can be configured with multiple edgeservers that cache the assets of the original or the host server.
When a user visits your website and request a static assets such as images or JavaScript file, the request is routed to the nearest edge server by the CDN, that content is available here. If the asset is not being cached at the edge server or a caching asset expire CDN caches bring the latest version from the source server or CDN edge servers around the other. If the CDN edge in the cache entry for the asset (if received moderate traffic from the Web site must generate the majority) will return the cached copy to the end user.
This geographically distributed users over can import content directly from the cache, minimizing the number of hops required to receive a static content near the edge. As a result, the faster latency and packet loss significantly reduces page load time significantly reducing the load on the source infrastructure.
Benefits of Using a CDN.
Origin Offload
Lower Latency for Improved User Experience
Manage Traffic Spikes and Avoid Downtime
Reduce Costs
Increase Security
How Does a CDN Work?
When a user visits a Web site, you first receive a response from the DNS server that contains the IP address of the host web server. Then your browser requests a web page content consisting of multiple static files such as HTML pages, CSS style sheets, JavaScript code and images.
Rollout of the CDN and manually "push (push out)" or CDN is (you both mechanisms discussed in the next section) automatically "pull" the asset as if the following CDN server Avon offload static assets web server links to point to a file that is hosted CDN creates a link to the static content again. If you are using a CMS such as WordPress rewrite links it can be achieved by using a third-party plug-ins, such as CDN Enabler.
 |
| PUSH CDN |
 |
| PULL CDN |
Many CDN supports custom domain so that you can create a CNAME record that points to the CDN endpoint in the following domains. The CDN routing requests to this endpoint (located much closer to the edge than the user's back-end server) The closest (Point of Presence) PoP user receives a user request. The PoP is configured with one or more of the CDN edge server deployment in Internet Exchange Points (IxP), a data center that is used to essentially Internet Service Provider (ISP) interconnect network. Then, the internal load balancer is one of the CDN edge server to route the request in the PoP and then provide content to users.
Conclusion.
Content delivery network can be a quick and effective solution for improving the scalability and availability of Web sites. By caching your static assets in geographically dispersed network, network optimization, you can significantly reduce latency and page load times for end users. In addition, you can use the CDN absorb the user's request, and greatly reduce the use of bandwidth in response to the edge cache will reduce the bandwidth and infrastructure costs.
Thanks to being here.
Comments
Post a Comment