O projeto 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

Tópicos recomendados:

Bitcoin Mining - Blockchain Technology - Network Optimization via TOFFEE Data-Center WAN Optimization ↗
Saturday' 13-Mar-2021
Bitcoin Mining - Blockchain Technology - Network Optimization via TOFFEE Data-Center WAN Optimization

Building my own CDN - Minify Script files - Update: 23-July-2016 ↗
Saturday' 13-Mar-2021
One of the suggestions Google PageSpeed Insights tool suggested for The TOFFEE Project website is to minify the css and java script files. Minify Script files: When you read online about minification of your web script files, often they highlight file size savings and thus resulting faster download time and better website performance.

LoRaWAN - Network Optimization via TOFFEE WAN Optimization ↗
Saturday' 13-Mar-2021
LoRaWAN - Network Optimization via TOFFEE WAN Optimization

TEST CASES :: TEST RESULTS :: TOFFEE-Mocha-1.0.14 Development version ↗
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.

TOFFEE (and TOFFEE-DataCenter) deployment with VPN devices ↗
Saturday' 13-Mar-2021
In case if you need to deploy TOFFEE along with your existing VPN devices you can deploy the same as shown below. This will allow your VPN devices to encrypt your TOFFEE WAN Optimized network data. NOTE: Make sure about the VPN deployment topology done in the right order. Else TOFFEE (LAN side) may get VPN encrypted packets which may not be possible (and or difficult) to further optimize. Hence always make sure to deploy them in a topology suggested below so that TOFFEE devices are out of VPN tunnel.

How to check a website using CDN ? ↗
Saturday' 13-Mar-2021

Power consumption of my Home Lab devices for research ↗
Saturday' 13-Mar-2021
Here is my power-consumption measurements of various devices deployed within my home lab. I measured via my kill-a-watt sort of power-meter which is fairly reliable and accurate. I checked its accuracy with various standard load such as Philips LED laps and other constant power-consuming devices to make sure that the power-meter is precise.

Demo TOFFEE-DataCenter WAN Optimization VM Test Setup ↗
Saturday' 13-Mar-2021

TCP Tune-up and Performance Analysis Graphs - Congestion Control - Research - Dos and Don'ts ↗
Saturday' 13-Mar-2021

Featured Educational Video:
Assista no Youtube - [435//1] 0x1d3 Who gets Laid off (or Fired) during a recession ? #TheLinuxChannel #KiranKankipati ↗

Demo TOFFEE-DataCenter WAN Optimization VM Test Setup ↗
Saturday' 13-Mar-2021

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

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

MySQL Database Network Data - WAN Acceleration ↗
Saturday' 13-Mar-2021
Here is a quick demo of TOFFEE WAN Optimization optimizing MySQL Data transfers of a MySQL Client to Server Remote Access.

Bulk Ping Tests - WAN Acceleration ↗
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