It appears to me that Node.js is more suited for "simple" "applets".

I'm too new to node to argue against this claim. But I do know that node is being used by companies like Walmart, LinkedIn, PayPal, NetFlix, Dow Jones, and more. Walmart released node on Black Friday of 2013 to handle their mobile traffic (about half of all traffic). LinkedIn is using node for all of their mobile. Are the companies just listed using node for "simple applets," as you are conceiving simple applets?


Kelly Cookson
IT Project Leader
Dot Foods, Inc.
1.217.773.4486 ext. 12676

-----Original Message-----
From: WEB400 [mailto:web400-bounces@xxxxxxxxxxxx] On Behalf Of Nathan Andelin
Sent: Thursday, October 15, 2015 6:43 PM
To: Web Enabling the IBM i (AS/400 and iSeries)
Subject: Re: [WEB400] Hosting a Large Number of Node Apps on the IBM i

A developer can also create "sub-apps" or modules within a "node app"
using ExpressJS router and module.exports. "Sub-apps" do not have
their own port numbers.

Here's a little bit of trivia; when I click on the link to "expand" this conversation in Gmail, it leads to a 1.8 Megabyte download. Maybe someone should start a new thread ;-)


It appears to me that the idea of "sub-apps" in Express.js is a "router"
within a "router". A "sub-app" is NOT an otherwise functional application, if I understand correctly.

Given the already obscure interface exposed by Express.js, their idea of "routers" within "routers" or "apps" within "apps" becomes even less clear.

They use regular expressions including wild-card characters to compare "routes" to URL "paths" which is another difficult concept. There is quite a bit of "overhead" in matching URLs with regular expressions.

After more thought, I'm still hung-up on the "necessity" of restarting a Node.js service every time a routing configuration changes, which occurs with every new "functional application" that is added to the service (every new URL which is defined). We're adding new applications to our Web portal daily during "sprints".

The need for an external router which includes fail-over support would be an absolute requirement. When you combine "applications" with "routing" and "HTTP services" in a single process, developers come up with all kinds of unforeseen ways to bring down the entire lot. Maybe it's as simple as a condition that results in a continuous loop. And it's unclear what may have caused it.

It appears to me that Node.js is more suited for "simple" "applets".
This is the Web Enabling the IBM i (AS/400 and iSeries) (WEB400) mailing list To post a message email: WEB400@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
or email: WEB400-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives at

This thread ...


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

This mailing list archive is Copyright 1997-2020 by 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].