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 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-2020 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].