TOFFEE项目
文档更新影片研究下载赞助商联系


RESEARCH 》 CDN Introduction - Content Delivery Networks or Content Distribution Networks

A Website without CDN Network: As everyone knows in a most common typical simplest scenario, you will have a website hosted in a web-server. In most common cases a typical small website will be hosted in some web-server, provided by web-hosting service provider. And the website DNS domain name points to this hosting web-server. In a simple scenario like this when the user requests the pages (or in general we can say any content such as text pages, images, and other media), the end-user’s browser request reaches this web-server, and the web-server delivers the web-pages via HTTP Protocol.
CDN Introduction website without CDN

Local user Browser Cache: The process of page or content download is pretty straight forward in a web-browser. A web-browser will have a small local cache. So that if there is any future repetitive requests, instead each time fetching from the main website (web-server), the browser will load/render the pre-cached content directly in the browser interface if it finds that specific content already once stored earlier in its cache. This saves up a lot of traffic. Since most of the times any website will have a lot of common content, such as logos, some Java scripts, CSS Stylesheets and so on. But the only drawback is that if there is a small organization, then each user have to access the content atleast once, so that they get their browser cache stored with content. In this case it is a highly discrete or non-shared cache platform/scenario.

Local web Proxy/Caching Servers: So in a office, or any such setup, where there are N users accessing common Internet resource, we can deploy a common web proxy or caching server(s). These servers (or a server) will create a great opportunity of creating a localized common caching scenario. So in this mode assume if one user accesses a website for first time, assume few of its contents are cached in this caching server, then later that day whichever other user accesses the same content, they may receive cached content from this central caching/proxy server. This is a huge advantage. Once the cache is mature and holds enough cached contents, it will sometimes exponentially reduce the network load, and downloading repetitive data from Internet (or any network in general).

A Website via CDN Network: In this scenario, the main basic website acts much like a source or origin. It will contain the web-content but it will not serve the real end-users. Instead there is going to be a CDN Service provider, and his vast infrastructure with several distributed, so called CDN Nodes across Internet spread globally. When the end-user requests the website, it is these CDN caching nodes will actually server the content to the end users. The job of the CDN service provider is to provide a highly redundant load-sharing along with transparent/abstract infrastructure. The CDN provider will often point or assign a CDN node which is least used at that instance, also sometimes assigns dynamically a CDN Node which is geographically nearer to the end-user. Hence this reduces the download time, since it reduces the number of router hops in internet.
CDN Introduction website with CDN

A CDN Node is often a highly proprietary caching resource installed by the CDN Service provider, where when it gets a request of a content to be served from end-user browsers, it caches the pages/content from its neighboring CDN Nodes, or sometimes directly from the origin web-servers. So this will exponentially reduces the load on the origin webserver. It is like with CDN server, the load on the origin webserver is or can be reduced upto 70-80% or sometimes even more depending on the content nature and depending on static vs. dynamic content it has.

So this is how a basic CDN works, its significance and value addition for any website if it is served to users via CDN, versus served directly via single webserver (or just few redundant web-servers) without a CDN.

Apart from this there are various advantages in using a CDN within your deployments. To know more about CDN Advantages kindly read the full detailed article HERE.



Suggested Topics:


Generic CDN


Building my own CDN

💎 TOFFEE-MOCHA new bootable ISO: Download
💎 TOFFEE Data-Center Big picture and Overview: Download PDF


推荐主题:

Building my own CDN - Finally Completed - Update: 17-Dec-2017 ↗
Saturday' 13-Mar-2021
Today I finally completed building my own private CDN. As I discussed so far in my earlier topics (Building my own CDN), I want to custom build the same step-by-step from scratch. And I don't want to for now use/buy third-party CDN subscriptions from Akamai, CloudFlare, Limelight, etc as I discussed earlier.

A study on Deep Space Networks (DSN) ↗
Saturday' 13-Mar-2021
When you are dealing Deep Space Networks (DSN) one among the most challenging parts is the Interplanetary distances and communicating data across such vast distances. This is where we are not dealing with common Internet type traffic such as HTTP/FTP/VoIP/etc but it is completely different when it comes to DSN so far. So optimizing data in DSN becomes mandatory. For example if you think one of the Mars Rovers, they have used LZO lossless compression.

CDN Introduction - Content Delivery Networks or Content Distribution Networks ↗
Saturday' 13-Mar-2021

First TOFFEE-Butterscotch Code Release ↗
Saturday' 13-Mar-2021
TOFFEE-Butterscotch is a variant of TOFFEE can be used to save and optimize your Home/SOHO Internet/WAN bandwidth. Unlike TOFFEE (and TOFFEE-DataCenter) TOFFEE-Butterscotch is a non peer-to-peer (and asymmetric) network optimization solution. This makes TOFFEE-Butterscotch an ideal tool for all Home and SOHO users.

YouTube Video Network Traffic Optimization - WAN Optimization Demo ↗
Saturday' 13-Mar-2021

TOFFEE DataCenter WAN Optimization - Google Hangouts demo and VOIP Optimization ↗
Saturday' 13-Mar-2021
TOFFEE DataCenter WAN Optimization - Google Hangouts demo and VOIP Optimization



TOFFEE-DataCenter Download :: TOFFEE-DATACENTER-1.2.2-1-portable ↗
Saturday' 13-Mar-2021

Building my own CDN - Moving away from Joomla to non-Joomla website - Update: 01-Oct-2016 ↗
Saturday' 13-Mar-2021
Seems there are couple of Inmotionhosting servers are down. And one of the server includes The TOFFEE Project website hosted server. I was in touch with the Inmotionhosting team trying to resolve the same. I found a unique issue that all my website files are intact and the Joomla database. But the Joomla database tables are completely wiped out and missing. Besides there is also a sort of upgrade going on in their servers. Luckily I have the most recent backup of the entire website.

Streaming CDN Types ↗
Saturday' 13-Mar-2021

Moon Base and Space Colonization - First we need fast InterPlanetary Internet ↗
Saturday' 13-Mar-2021



Featured Educational Video:
在YouTube上观看 - [928//1] x23e TrueNAS ZFS Pool Resilver over and over again issue | ZFS NAS Storage | Forever Resilver ↗

Replacing in Lab Intel Core i7 5820K Desktop PC with Intel Celeron 1037U Mini-PC ↗
Saturday' 13-Mar-2021
As a research experiment I replaced my Intel Core i7 5820K desktop PC with my Intel Celeron 1037U Mini-PC as my everyday desktop system. This is an attempt to reduce my overall monthly power consumption. As well an attempt to do feasibility tests and research to know how far Mini PC will dominate the market in future and to study the real potential of Mini PCs.

TEST CASES :: TEST RESULTS :: TOFFEE-Mocha-1.0.14 Development version ↗
Saturday' 13-Mar-2021

A study on Deep Space Networks (DSN) ↗
Saturday' 13-Mar-2021
When you are dealing Deep Space Networks (DSN) one among the most challenging parts is the Interplanetary distances and communicating data across such vast distances. This is where we are not dealing with common Internet type traffic such as HTTP/FTP/VoIP/etc but it is completely different when it comes to DSN so far. So optimizing data in DSN becomes mandatory. For example if you think one of the Mars Rovers, they have used LZO lossless compression.

TOFFEE hardware selection guide ↗
Saturday' 13-Mar-2021
When you build a WAN Optimization device with TOFFEE the entire packet processing (data optimization) takes place in software layer or in other words more precisely Operating System kernel space. However if you have any compression or encryption hardware accelerator hardware card the parts of the TOFFEE packet processing modules can be offloaded to hardware layer and thus improving its efficiency.



在YouTube上观看 - [1882//1] Deep Space Communication - Episode1 - Introduction ↗

TOFFEE-Mocha Documentation :: TOFFEE-Mocha-1.0.18-1-x86_64 ↗
Saturday' 13-Mar-2021



Research :: Optimization of network data (WAN Optimization) at various levels:
Network File level network data WAN Optimization


Learn Linux Systems Software and Kernel Programming:
Linux, Kernel, Networking and Systems-Software online classes


Hardware Compression and Decompression Accelerator Cards:
TOFFEE Architecture with Compression and Decompression Accelerator Card


TOFFEE-DataCenter on a Dell Server - Intel Xeon E5645 CPU:
TOFFEE-DataCenter screenshots on a Dual CPU - Intel(R) Xeon(R) CPU E5645 @ 2.40GHz - Dell Server