Skip to content

noradle connection architecture

Jump to bottom
kaven276 edited this page Jun 10, 2016 · 9 revisions

about submodules

note: from v0.14.0, noradle is split into several sub projects under https://github.com/noradle.

it's for those considerations:

  • deploy only the sub-module you require, for example, in one server, you deploy noradle-dispatcher only
  • each submodule is focused on one goal, easy to manage
  • each submodule will evolve itself, allow contributors to improve just the submodule they are interested in
  • each submodule represent a special aspect of noradle, doc/wiki will distributed among them, no longer a mess all in the main project
 {{browser}}  -----------(http)-------------->  {{1.noradle-http}} ---      / {{noradle-console}}
http client                                   /                       \    /
     \--------(http)-> {{proxy(nginx)}} -----/              {{{noradle-dispatcher}}} <------ {{oracle}}  
                              \----(SCGI)---->  {{2.noradle-scgi}} ----/ /
                               \---(FCGI)---->  {{3.noradle-fcgi}} -----/    
                                     (note: 123 require {{noradle-nodejs-client}} )

so you can see, noradle-dispatcher is the center node in noradle connection architecture.

the submodule list, all under github noradle

note:
noradle-scgi(2)/noradle-fcgi(3) have been given up, because they add additional layer in the path to oracle, as a result, all scgi/fcgi acceptance will be implemented in noradle-dispatcher.

Clone this wiki locally