Skip to content
⭕ N2O TT: Application Server
Branch: master
Clone or download
Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
doc
include
man
priv n2o.js/onbert: p is no longer a global variable Feb 27, 2019
src ftp Nov 22, 2018
test Delete bert.sh Dec 11, 2018
.gitignore
.travis.yml
CNAME
CONTRIBUTORS.md md Nov 15, 2018
HISTORY.md md Nov 15, 2018
LICENSE
README.md
index.html index Dec 2, 2018
rebar.config
sys.config

README.md

N2O: Distributed Application Server

Build Status

N2O is a embeddable message protocol loop library for WebSocket, HTTP, MQTT and TCP servers. It provides basic features, such as: process management; virtual nodes ring for request processing; session, encoding, mq, cache and log services. It also includes poor man's bridges to server's endpoints.

Features

  • Purpose: High performance protocol relay
  • Endpoints: WebSockets, MQTT, TCP
  • Codebase: 1K LOC
  • Buildtools: REBAR, MAD
  • Templates: DTL, NITRO
  • Hosts: COWBOY, EMQ, MOCHIWEB
  • Samples: REVIEW (1), SAMPLE (2)

Idea

N2O was created to bring clarity and sanity to software development. The distribution model is per file basis with ISC license.

Kernel

The core modules provide OTP start and N2O entry point.

MQTT

MQTT version is implemented as RPC over MQ pattern. N2O service worker started as ring of virtual nodes each runs N2O loop.

$ mad app mqtt review
$ cd review
$ mad dep com pla rep
$ open http://127.0.0.1:8000

WebSocket

N2O Loop is directly connected and runned inside context of WebSocket handler. Usually in Erlang we use syn or gproc OTP message buses. As such buses are optional in MQTT setup we include bus drivers in WebSocket package.

$ mad app web sample
$ cd sample
$ mad dep com pla rep
$ open http://127.0.0.1:8001/app/index.htm

Protocols

N2O is shipped with 3 protocols, which could be omited or extended.

Services

Formatters, Loggers, Sessions, etc. Optional.

JavaScript

Literature

You can’t perform that action at this time.