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


おすすめトピック:

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

Demo TOFFEE-DataCenter WAN Optimization packaging feature ↗
Saturday' 13-Mar-2021

Bulk Ping Tests - WAN Acceleration ↗
Saturday' 13-Mar-2021

TOFFEE Data-Center optimized Internet of Things (IoT) Platform ↗
Saturday' 13-Mar-2021

TOFFEE (and TOFFEE-DataCenter) optimized Satellite (inflight/marine/defense) ISP Networks ↗
Saturday' 13-Mar-2021
TOFFEE Optimized Satellite ISP Network: TOFFEE/TOFFEE-DataCenter can be used to optimize Satellite Networks (Satellite based Internet Networks, VoIP, Data, private leased-links) as shown. Ground station transponders can be connected via array of TOFFEE Devices and in the remote CPE can have dedicated or inbuilt TOFFEE with which you can establish a WAN Optimized Satellite Network Tunnel as shown.

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

Youtubeで見る - [1888//1] Deep Space Communication - Episode1 - Introduction ↗


TOFFEE-Mocha Documentation :: TOFFEE-Mocha-1.0.32-1-x86_64 and TOFFEE-Mocha-1.0.32-1-i386 ↗
Saturday' 13-Mar-2021

Tweaking Network Latency - Live Demo - via TOFFEE-DataCenter ↗
Saturday' 13-Mar-2021

Internet optimization through TOFFEE-DataCenter WAN Optimization Demo ↗
Saturday' 13-Mar-2021
Internet optimization through TOFFEE-DataCenter WAN Optimization Demo

Building my own CDN - choosing a web-hosting to deploy my CDN - Update: 28-July-2016 ↗
Saturday' 13-Mar-2021
The TOFFEE Project website is hosted on Inmotion Hosting. And so I am looking for alternate hosting provider to build my first CDN node. My plan is to make multiple sub-domains of my website such as cdn1.the-toffee-project.org, cdn2.the-toffee-project.org and point each of this corresponding subdomain(s) to various alternative web hosting servers geographically spread across the world. Sometimes choosing the same vendor for multiple CDN nodes may result multiple servers existing in the data-center. And this becomes an issue if there is some catastrophic network disaster.



Featured Educational Video:
Youtubeで見る - [8613//1] x254 Kernel Init Code without Kernel Module - Kernel Programming Tip #linode ↗

TOFFEE Benchmarks :: TOFFEE-1.1.28 ↗
Saturday' 13-Mar-2021
Here is the TOFFEE WAN Optimization benchmarks of the TOFFEE version: TOFFEE-1.1.28. This is the current TOFFEE development version till date (2-Jul-2016). This is a HPC TOFFEE variant meant for high-end custom build servers and high-end desktops (i.e High Performance Computing a.k.a HPC). TOFFEE built this way often needs customized kernel compilation and build such as processor specific and hardware specific tune-ups since it is highly CPU intensive (if not offloaded via Hardware Accelerator Cards).

Skype VOIP Data - WAN Acceleration ↗
Saturday' 13-Mar-2021

Live demo - Data Transfer - High bandwidth to Low bandwidth ↗
Saturday' 13-Mar-2021
I always wanted to do some real experiments and research on packet flow patterns from High-bandwidth to Low-bandwidth networks via networking devices. This is something can be analyzed via capturing Network stack buffer data and other parameters, bench-marking, and so on. But eventually the data-transfer nature and other aspects is often contaminated due to the underlying OS and the way Network stack is implemented. So to understand the nature of packet flow from Higher to Lower bandwidth and vice-versa such as Lower to higher bandwidth, I thought I experiment with various tools and things which physically we can observe this phenomena.

TOFFEE-Butterscotch Bandwidth saver software development - Update: 17-Nov-2016 ↗
Saturday' 13-Mar-2021
Here is my second software development update of TOFFEE-Butterscotch. In the previous update (28-Oct-2016) I discussed about the Alerts, etc. Whereas in my first TOFFEE-Butterscotch news update I have introduced about TOFFEE-Butterscotch research, project specifications, use-cases, etc.



Youtubeで見る - [889//1] 280 WAN Optimization - Animated demo of Packet Optimization in TOFFEE-DataCenter ↗

DIY TOFFEE WAN Optimization Device with Intel Celeron Mini PC ↗
Saturday' 13-Mar-2021
Here is a step-by-step DIY to build your own Intel based Mini PC WAN Optimization Device with TOFFEE. I chose this below Intel Celeron Mini PC since it is fan-less aluminium case and as well it has 2 dedicated inbuilt Gigabit Ethernet ports. You can use one for LAN Network and one for WAN Network.



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