×
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.
Configuring 1 "load-balancer" and routing to 3 Node HTTP instances for each
Department (9 total Node instances).
Although that ensures scaling and fail-over support, one question is
whether the "applications" which are being run in those instances might
need to share session data with each other?
Once a request "hits" a Node HTTP instance, further routing needs to take
place:
That again raises the question about how effective Express.js or some other
framework might be at configuring and routing potentially long lists of
URLs to appropriate JavaScript routines? And how disruptive to users as
"restarts" are required when routing configurations change?
I'd rather not dive into how effective Java or PHP might be at "scaling",
"fail-over", "request-routing", "application deployment", support for
"multiple environments" (development, testing, production). You basically
end up talking about running multiple virtual machine instances, and in the
case of Java, hiring more people to manage the complexity (much like .Net).
As an Amazon Associate we earn from qualifying purchases.
This thread ...
Re: Hosting a Large Number of Node Apps on the IBM i, (continued)
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
