×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
On Wed, Mar 21, 2018 at 4:31 PM, Kelly Cookson <KCookson@xxxxxxxxxxxx>
wrote:
Hi Nathan,
I'm having a hard time reconciling two claims: (a) Node actually performs
less well than synchronous programming technologies, and (b) businesses
that do high volumes of web transactions say Node allowed them to process
more transactions more quickly while reducing the number of servers they
needed. These two things are causing a lot of cognitive dissonance in me.
I understand where you're coming from. You've heard big picture claims
about Node's efficiency and performance. I don't doubt the truth of them.
Then I offer a micro perspective picture into Node's architecture that
deals only with the performance impact of Node's event loop on Javascript
functions that implement async-await keywords. And that picture is
supported by benchmarks too.
What can we learn from both perspectives? I would suggest that Node.js is
really efficient at certain things, but can become really bogged down by
others. That it behooves application architects and engineers to know what
(and what not) to use Node.js for.
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.
midrange.com
