​Some good commentary on how to organize larger Node projects: ​
http://stackoverflow.com/questions/9832019/how-to-organize-large-node-js-
projects



Thanks for your reply, Aaron. However, my question was in regards to having
a separate Node process for each "application". The Stack Overflow
discussion (in contrast) offered tips about organizing code within a single
Node process.

I'm interested in hearing the pros and cons of running multiple Node
processes (i.e. one per application) vs. having a single Node process which
may organize the code by dispatching individual requests to various
in-process modules (JavaScript files).

If each application were a separate Node process, a reverse proxy might be
used to route browser requests to individual Node processes (i.e.
app1.domain.com may be routed to a Node process which is listening on port
9001 while app2.domain.com may be routed to a Node process which is
listening on port 9002, etc.).

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2022 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.