Re: Question about Node.JS and XMLSERVICE

That brings us back to the question of what types of workloads are

appropriate for Node and what types should be handled by separate IBM i
JOBS?

I think to answer this question you need to convey the various workload
options we have to pick from.

For example, it's been documented that Node.js shouldn't be used for
calculation intensive applications.

Aside from workload type uses there are also scenario uses for open source
languages. For example, I find it's much easier to write non-web scripts
in <open-source-language> for IFS purposes than to do the same thing with
RPG. For example, a run-from-a-shell-prompt script to manually update
database rows based on some selection criteria.


Aaron Bartell
litmis.com - Open Source and IBM i. No Limits.


On Fri, Aug 28, 2015 at 9:48 AM, Nathan Andelin <nandelin@xxxxxxxxx> wrote:

It explains what the event loop in node is, and why it's important to

node

performance.

I agree, that presentation was a good explanation of how Node works, and
why you should never do anything that would block Node's event loop for
extended periods of time.

Understanding the event loop also helped me understand why node is an
opinionated development tool.

Good point. Application code should "dispatch" work to threads and register
callback functions to handle responses. Don't do anything that would block
Node from monitoring its event queues and triggering callback functions.

You may "dispatch" a Node thread to monitor for HTTP requests and
"register" a callback function to handle those events. That callback
function may subsequently "dispatch" an SQL statement to another Node
thread and "register" another callback function to handle the SQL response
which will eventually show up on one of Nodes event queues.

That brings us back to the question of what types of workloads are
appropriate for Node and what types should be handled by separate IBM i
JOBS?
--
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.