To reduce server load, latency and establish self-maintainable CDN based on your users browsers.
npm -i viraljs
var ViralContainer = require('viraljs');
var viralContainer = new ViralContainer();
myExpressApp.use(viralContainer.middleware);Isomorphism blurred boundaries between server and client. The only difference between them currently is server`s ability to distribute application to clients. What if we go further enabling client to do this? What if we erase boundaries between server and client completely? In this case every client which got application`s code becomes it`s distributor or carrier. And drawing the analogy with spreading microorganisms in the nature this technique perfectly matches “viral JavaScript“ naming.
P2P content distribution allows to reduce server load and decrease network latency since peering could be setup in the way content to be delivered from the nearest peer available. For example after hitting corporative network application will be delivered inside of it using high speed internal channels without creating a load on company`s internet channel.
Traditional app distribution. Server sends package many times, corporative internet channels are loaded appropriately
In case of P2P distribution application hits corporative network once and then is distributed using high speed internal network. This reduces server load and corporative internet channel load
Or another case – once application got from USA to Europe it is delivered inside of European networks only without creating transatlantic traffic.
It takes a lot of transatlantic trips to transmit an app when doing it in a traditional way
P2P allows to reduce number of transcontinental transfers and reduce server load
By distributing application via P2P you create a self-establishing and self-evolving CDN which moves data closer to client.
Have a bug? Please create an issue here on GitHub!
https://github.com/PixelsCommander/ViralJS/issues
Copyright 2015 Denis Radin aka PixelsCommander