Thank you for the reply, I did come across your product. So if you put any work into getting Google to bring up your product, it worked.
I cannot use any application management system until I solve the problem of being able to run 10,000 instances of an "app". Ultimately I have control over how these apps are written so I can create a framework in nodejs that was essentially a nodejs fragment. But I like the idea of creating a system that allows one to run the app outside of the system as well as inside of it. In all reality, without writing an app framework, I'll have this same issue in Erland and Java. Spawning 10,000 threads in Java is also unreasonable and smells of a bad design. Clustering multiple of these "apps" in a single nodejs isn't out of the issue. But they would have to be agnostic as to which apps are running and I would need to control how many apps run in X number of nodes. I saw threads a gogo and thought this would help but after reviewing it, it solves another issue I was having (CPU intensive calculations). I think I may have a design issue to work out first that has nothing to do with NodeJS. I have looked at Erlang before, mostly because that is what RabbitMQ was written in. I really like what nodejs would give me. The ability to write short, event driven I/O applications. That is exactly what I need. It's just a matter of finding a way to run thousands of these. The requirements are: Apps should be code complete. All the code needed to run the app is there (no fragments) Apps cannot bring down other apps if they crash -- Job Board: http://jobs.nodejs.org/ Posting guidelines: https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines You received this message because you are subscribed to the Google Groups "nodejs" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/nodejs?hl=en?hl=en
