On Mon, Mar 19, 2018 at 7:24 PM, Nathan Andelin <nandelin@xxxxxxxxx> wrote:
I'm curious too. Particularly if the "batch script" were performing any DB
I/O. Why would you do that in Node.js?
I'm in the same camp here with async operations for most DB, especially
retrieving data. I hear the argument "but your program can go and do this
and that while the result set is being retrieved". That's the whole
point.. I need that result set before I can continue on! :)
Updating, inserting and deleting for the most part can be anynch, but when
IBM switched to async and stopped updating or supporting the sync db
functions I think it's a mistake. Especially if you're doing business
programming.
Otherwise async is a pretty cool feature for other things, but not
everything.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 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].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.