Re: Hosting a Large Number of Node Apps on the IBM i

[Nathan Andelin <nandelin@xxxxxxxxx>]

Kelly,

It's nice to see questions which are relevant to the deployment of broadly
scoped systems. And I agree that the answer always seems to come back to
"routing".

I'm not sure how to answer your questions about options 1 - 3, so I'll ask
more questions which might provoke thought.

What would be the best tool for handling:

1. Request logging?
2. Response logging?
3. Gzip compression?
4. TLS encryption?
5. Serving static content?

One benchmark I came across showed IIS performing 2.5 times faster than
Node.js while serving static content, presumably due to caching. Apache
offers similar caching. Wait for a Node.js caching module? Build one
yourself?

Node.js experts seem to advise the avoidance of any computationally
intensive work within the main event loop. Would "computationally
intensive" include the evaluation of "routing" expressions?






On Tue, Oct 13, 2015 at 12:32 PM, Kelly Cookson <KCookson@xxxxxxxxxxxx>
wrote:

> If our shop adopts node, we would probably use it to develop web and
> mobile apps instead of 5250 green screens (for future development). Over
> the years, we have accumulated a large number of 5250 green screen
> interactive programs. If we adopt node, I can imagine we will accumulate a
> similarly large number of node apps.
>
> The way to host a large number of node apps is, according to my Google
> searches, routing. But there are different strategies for routing.
>
> 1. Use a reverse proxy to route requests to node apps, where each node app
> has its own URI and port number. The reverse proxy could be a web server or
> something like node-http-proxy. Redbird also appears to be a package for
> setting up a reverse proxy for node apps (
> https://github.com/OptimalBits/redbird?utm_source=nodeweekly&utm_medium=email
> ).
>
> 2. Use ExpressJS vhost to route requests to node apps, where each node app
> has its own URI and port number.
>
> 3. Use ExpressJS routers and module.exports to route requests to node
> sub-apps or modules (something like this: https://vimeo.com/56166857).
>
> So, I am left with a few questions. What strategy or combination of
> routing strategies would be best for ensuring high availability of node
> apps? What strategy or combination of routing strategies would be best for
> scaling node apps (e.g., using the cluster module)? Is reducing the number
> of unique ports being listened to by node apps a good reason for using the
> sub-apps strategy (option #3 above)?
>
> Thanks,
>
> Kelly Cookson