The TOFFEE Project
HOMEDOCUMENTATIONUPDATESVIDEOSRESEARCHDOWNLOADSPONSORSCONTACT


RESEARCH 》 Building my own CDN - Finally Completed - Update: 17-Dec-2017

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.

As you know The TOFFEE Project (or TOFFEE) is a fork of my TrafficSqueezer WAN Optimization project. I still have/own the TrafficSqueezer domain which is www.trafficsqueezer.org. But ever since I started the The TOFFEE Project fork (and the website), I did a direct domain redirect to the new registered www.the-toffee-project.org. But now recently I got a new hosting from GoDaddy, so once again I linked the old domain (i.e. www.trafficsqueezer.org) to that new hosting. Hence now I have a fresh initial welcome page in the www.trafficsqueezer.org mentioning about the project status. And it automatically redirects the users to the new The TOFFEE Project website (i.e. www.the-toffee-project.org, as you can see in the screenshot below). Other than this, the website is completely empty. Which means I can use the hosting space for other important situations like in this case to build my own private CDN for the www.the-toffee-project.org website.
01 Building my own CDN for TOFFEE website - empty TrafficSqueezer website

Creating a new sub-domain to host my new CDN cdn.trafficsqueezer.org:
So I went ahead and created the new sub-domain cdn.trafficsqueezer.org in my GoDaddy portal (as shown below) to host the CDN within the same so that it is sort of isolated from the main website context. It also makes easy to track the GoDaddy cPanel Awstats and so on.
02 Building my own CDN for TOFFEE website - cdn.trafficsqueezer.org - sub-domain to host my new CDN [CDN]
03 Building my own CDN for TOFFEE website - cdn.trafficsqueezer.org - sub-domain to host my new CDN [CDN]

When I create this sub-domain, I have a choice, suppose if I have more websites, I can even instead create sub-domain names such as cdn-the-toffee-project-org and so on, so that this way we can have each CDN sub-domain created for a dedicated remote site. But in my case I would like to keep things simple at this point so I created for now a single sub-domain such as cdn.trafficsqueezer.org and hosted(copied) the images and other web-resources within the same.

So with this thing in place, I now changed my main website scripts so that they point these resources dynamically as per the mode I want. Such as:

  • Always CDN mode
  • Load-Sharing CDN mode
  • No CDN mode (or Disable CDN mode)

Unfortunately, for security reasons I am not interested to share this logic(my exact code). But anyways I hope you get the idea how it can be done. The Always CDN mode allows registered resources (images/scripts/etc) to get incorporated always via CDN for each page request. While the load-sharing CDN mode gives me the flexibility to use CDN resources fairly. And this way if I choose to host in other CDNs in future such as this, I can dynamically point to CDN of my choice dynamically in a sort of round-robin fashion. But for now since I have only one CDN, sometimes the images(and resources) will be served from CDN sources and sometimes it will be served locally via www.the-toffee-project.org server itself.

Last but not least I did the No CDN mode or Disable CDN mode as a precaution so that if something goes wrong or if the CDN site is down, the whole CDN stuff can be disabled. Even this can be automated by incorporating some sort of remote discovery and intelligent switchover to avoid any catastrophe!

So as you can see here are some few screenshots where at times some are getting fed via CDN and at times they are getting fed by www.the-toffee-project.org itself (i.e no CDN). Since it is still work in progress, to debug the same, I have incorporated this dynamic " [CDN]" string in the image title and image alt, so that it gives me a clue if the system is all working fine. And I should able to distinguish the image source.

Here are some of the screenshots. Notice the image title when I hover the mouse pointer above the same:

Image/Resource not fed via CDN (below):
04 Building my own CDN for TOFFEE website - cdn.trafficsqueezer.org - checking if the resource is fed via CDN

Image/Resource fed via CDN (below):
05 Building my own CDN for TOFFEE website - cdn.trafficsqueezer.org - checking if the resource is fed via CDN

Image/Resource fed via CDN (below):
06 Building my own CDN for TOFFEE website - cdn.trafficsqueezer.org - checking if the resource is fed via CDN [CDN]

Image/Resource not fed via CDN (below):
07 Building my own CDN for TOFFEE website - cdn.trafficsqueezer.org - checking if the resource is fed via CDN

And yes, like I discussed in my earlier CDN topic (How to check a website using CDN ?), you can do a view source of any of these pages (as shown below) just like Facebook, Twitter, etc, and get an hint whether a website is using CDN or not.
08 Building my own CDN for TOFFEE website - cdn.trafficsqueezer.org - check if a website is using CDN

Conclusion:
Like I discussed in this case it is not so sophisticated or complex like subscription based CDNs like what you get via CloudFlare/Akamai and so on. But instead this is a pure private custom-built CDN. And kindly note, even CDN technology is a sort of (or a specific category of) WAN Optimization technology. But it is not a mundane WAN Optimization technology, instead it comes under one among the Internet Optimization Technologies.

At times I do offer consultation on this regard to my clients across the world. And hence in case if you are looking forward for any expert advice or any other consultation on this regard you can contact me via email provided in the contact page.



Suggested Topics:


Generic CDN


Building my own CDN

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


Recommended Topics:

TOFFEE-DataCenter as a VNF for NFV ↗
Saturday' 13-Mar-2021

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.

TOFFEE-DataCenter WAN Optimization software development - Update: 13-Aug-2016 ↗
Saturday' 13-Mar-2021
Earlier the TOFFEE is intended to work on IoT devices, Satellite Networks, branch office/SOHO deployments. In most cases the users may deploy just one or couple of TOFFEE devices per site. But in the case of TOFFEE-DataCenter, users can scale-up deploying the same in multiple servers in a sort of distributed cluster computing scenario. Besides the core TOFFEE-DataCenter components (such as packet processing engine/framework), I need to do lot of changes in its Graphical User Interface (GUI) too to address these new requirements.

TEST CASES :: TEST RESULTS :: TOFFEE-Mocha-1.0.32 asymmetric constant packet delay feature ↗
Saturday' 13-Mar-2021

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

Demo TOFFEE_DataCenter WAN Optimization VM (in VirtualBox) Test Setup ↗
Saturday' 13-Mar-2021
Demo TOFFEE_DataCenter WAN Optimization VM (in VirtualBox) Test Setup



TOFFEE-DataCenter - First Live Demo and software development - Update: 26-Aug-2016 ↗
Saturday' 13-Mar-2021
Today I have done a test setup so that I can able to connect my Android Samsung Tab via TOFFEE DataCenter. Below is my complete test topology of my setup. For demo (and research/development) context I configured TOFFEE DataCenter in engineering debug mode. So I do not need two devices for this purpose.

Why TOFFEE is forked from TrafficSqueezer ↗
Saturday' 13-Mar-2021
TrafficSqueezer is an open-source WAN Optimization project. TrafficSqueezer is mainly a research project which is started around mid-2006. It is initially started as a research (or prototype) code even before it is officially registered in Sourceforge.net. But this code is just primitive user-space raw socket modules. This is later refined and a pre-alpha version is created. Followed by which Alpha release. This prototype code is moved from user-space to Linux Kernel (Kernel Space) and then the journey begin in terms of making a serious WAN Optimization solution. Once the pre-beta and beta releases are complete the mainstream series is started.

CDN Hosting ↗
Saturday' 13-Mar-2021
It is quite interesting that there are few web hosting firms are offering direct CDN based hosting services. Since it is a direct CDN based hosting, it is cheap, extremely easy or transparent CDN service. It is transparent, since each time you publish your content in the hosting web-server (origin server), it is immediately is in sync automatically in the user-serving CDN caching machines. Since the hosting vendor and the CDN vendor are all the same, it is also easy to use their services. There is no incompatibility issues, interoperability issues, and better integrated analytics, are all the benefits of CDN Hosting services.

TOFFEE WAN Optimization software development, roadmap, live-demo - Update: 06-Nov-2016 ↗
Saturday' 13-Mar-2021
Here are some of the screenshots of the new upcoming TOFFEE WAN Optimization release and live demo.



Featured Educational Video:
Watch on Youtube - [4073//1] 0x1c9 NAS OS | Expert's take on FreeNAS vs UNRAID | My two cents | Best Tips ↗

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

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.

TOFFEE (and TOFFEE-DataCenter) optimized Mobile Wireless Backhaul Networks ↗
Saturday' 13-Mar-2021
TOFFEE can be used to optimize expensive Wireless backhaul network infrastructure. TOFFEE can be deployed over existing slow or often outdated old backhaul networks too. This will leverage mobile ISPs and network service providers to reduce their bulk IT CapEx and OpEx Costs.

Why TOFFEE is forked from TrafficSqueezer ↗
Saturday' 13-Mar-2021
TrafficSqueezer is an open-source WAN Optimization project. TrafficSqueezer is mainly a research project which is started around mid-2006. It is initially started as a research (or prototype) code even before it is officially registered in Sourceforge.net. But this code is just primitive user-space raw socket modules. This is later refined and a pre-alpha version is created. Followed by which Alpha release. This prototype code is moved from user-space to Linux Kernel (Kernel Space) and then the journey begin in terms of making a serious WAN Optimization solution. Once the pre-beta and beta releases are complete the mainstream series is started.




Optimization of network data (WAN Optimization) at various levels ↗
Saturday' 13-Mar-2021
WAN Network data can be optimized at various levels depending upon the network applications, protocols, topology and use-cases. So the amount of data you can optimize will depend on the strategy you choose to optimize. Such as: Network Packet level optimization, Session level optimization, File level optimization, etc.



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