Ecosyste.ms: Awesome

An open API service indexing awesome lists of open source software.

Awesome Lists | Featured Topics | Projects

https://github.com/PixelsCommander/ViralJS

Express.JS middleware to enable P2P distribution for your app. Your decentralized CDN made easy.
https://github.com/PixelsCommander/ViralJS

expressjs nodejs p2p webrtc

Last synced: 9 days ago
JSON representation

Express.JS middleware to enable P2P distribution for your app. Your decentralized CDN made easy.

Awesome Lists containing this project

README 

        
![ViralJS](https://github.com/PixelsCommander/ViralJS/blob/master/figures/logo-small.png?raw=true)



ExpressJS middleware for P2P Web apps distribution

==================================================

To reduce server load, latency and establish self-maintainable CDN based on your users browsers.



[![Join the chat at https://gitter.im/PixelsCommander/ViralJS](https://badges.gitter.im/Join%20Chat.svg)](https://gitter.im/PixelsCommander/ViralJS?utm_source=badge&utm_medium=badge&utm_campaign=pr-badge&utm_content=badge)



- [Website](http://pixelscommander.github.io/Viral.JS/)

- [Demo](http://pixelscommander.com:3000)

- [Article about](http://pixelscommander.com/en/interactive-revolution/what-is-beyond-isomorphic/)



Installing from NPM

-------------------

`npm -i viraljs`



How to use?

-----------



```js

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.



Motivation

----------

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.



![Normal distribution](https://github.com/PixelsCommander/ViralJS/blob/master/figures/normal_m.png?raw=true)



Traditional app distribution. Server sends package many times, corporative internet channels are loaded appropriately



![P2P distribution](https://github.com/PixelsCommander/ViralJS/blob/master/figures/p2p_m.png?raw=true)



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.



![Normal distribution](https://github.com/PixelsCommander/ViralJS/blob/master/figures/normal_world_m.png?raw=true)



It takes a lot of transatlantic trips to transmit an app when doing it in a traditional way



![P2P distribution](https://github.com/PixelsCommander/ViralJS/blob/master/figures/p2p_world_m.png?raw=true)



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.



Bug tracker

-----------



Have a bug? Please create an issue here on GitHub!



https://github.com/PixelsCommander/ViralJS/issues



License

-------

MIT: http://mit-license.org/



Copyright 2015 Denis Radin aka [PixelsCommander](http://pixelscommander.com)