×
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.
I'm always open to other points of view.
There seems to be general agreement about external reverse-proxies /
load-balancers being an effective means of "routing" work to multiple
Node.js instances (Jobs), which ensures scalability and fail-over support.
There doesn't seem to be much distinction whether one uses IIS, NGiNX,
Apache, or whatever for external request routing.
It would be nice to see some benchmarks pertaining to Node's internal
load-balancing via the "Cluster" module. I'd be a bit wary of it after just
reading the documentation.
The question that has me the most stumped is the one about "routing"
potentially thousands of URLs to appropriate JavaScript routines, with each
routine pertaining to various "applications" within "modules" within
"major-system-areas" (however you organize you broadly-scoped services)?
Kevin indicated that Node has to be restarted each time a routing
configuration changes in Sails. Inline-coding of routes in Express
obviously suffers from the same problem. I'd be concerned about performance
as the number of URLs increase.
midrange.com
