Are you talking about optimistic vs. pessimistic locking(n1)?
Based on my readings I gather that you should never try pessimistic locking
in any Node service intended to support multiple concurrent users because
only one commitment boundary is available per JOB.
Optimistic locking is a good use case, and a good reason for managing
"stateful" database connections, since the logic involves comparisons of
before and after images of records forwarded to user's screens, with the
current image of the record last retrieved from the DB and intended for
update, and either persisting the changes to the DB or returning a message
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2021 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
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.