Re: Node Modules or Sub Apps (Was: Hosting a Large Number of Node Apps on the IBM i)

Nathan



"Node requires a restart when you make changes to the source code." – This
makes sense since it probably cashes files like a browser where you have to
press F5 to refresh your cache that simulates a fresh restart.



I read about Walmart’s setup, and I didn’t like what I read. Lots of load
balancing and virtual machines, passing data between servers in what they
call server zones with specific functions like logging – huh, it sounds
complicated for the relatively small web applications (read traffic) we has
to deliver on IBM I.



How many people does Walmart has to just administer their setup with all
these virtual machines?


We on IBM I have the luxury that we in most cases just can buy a bigger
server with more cores instead of employing an army of technical
administrators ;-)

On Fri, Oct 16, 2015 at 11:36 PM, Nathan Andelin <nandelin@xxxxxxxxx> wrote:

I'm open to hearing about other ways to conceptualize what a "node app"

is.

I watched that Youtube presentation on "modular" Node apps again. I had
actually viewed it a couple times before. Sometimes it takes an interval
mixed with additional reading before I "think" I understand something.

Express.js and Jade.js are obviously featured in the video. The author used
the term "app" in the context of a "main app" which is listening on an HTTP
port. "App" was also used in the context "routing" from the main app to
sub-apps.

The author's idea of sub-apps (evidently within an Express.js framework)
seemed to be scoped to handle just one browser request; The request for the
Login page, for example.

As you may understand from my previous posts, I find this application
architecture problematic, at best. A sub-app is a request-route to a page?
Are they kidding us? Restarting an HTTP service every time a "page" is
modified?

So, I'm having difficulty conceptualizing what a "node app" should be.

Regarding your point about a Node app serving as a "proxy", that appears to
be somewhat inline with Walmart's setup.

https://gist.github.com/hueniverse/7686452

I could imagine a Node service writing "request.body" to a stream file,
which effectively becomes STDIN for an IBM i ILE JOB, which handles the
request and generates a separate output stream (effectively STDOUT), which
Node picks up and returns to the browser.
--
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,
visit: http://lists.midrange.com/mailman/listinfo/web400
or email: WEB400-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/web400.