JBoss AS 7 and Node.js hype -
i dont want compare apple orange, done, example, in:
http://blog.shinetech.com/2011/06/10/nodejs-from-the-enterprise-java-perspective/
http://adamgent.com/post/10440924094/does-java-have-an-answer-to-node-js
actually, not have concurrency problem jboss 7, if had on, should do?
should i:
solution i:
horizontal/vertical scale
use httpd in front of jboss as
use @asynchrounous or messaging systems (such akka) tasks
...
solution ii:
- use node.js (rhino.js)
can provide practical experiences jboss 7 failed scale? have never had such experiences myself.
for example, imagine web application 10.000.000 concurrent request *on single machine* (with single jboss-as-instance or single node.js-instance).
what result?
would node.js works while jboss 7 crash?
in general, java ee targetted @ high-scale application , of design decisions comply that, persistence on session , cache replication view layers.
while node.js may tasks, java ee 6 (imo) if want use whole stack.
there's more comming regarding scalability, jsr-352. java ee yet improve.
regarding question - "while jboss 7 crash" - doesn't crash. it's faulty or poorly written application crashes. node.js gives api. java ee gives multitude of apis, misused or conceptually misunderstood, results in problems outofmemoryexception. designed application, there should no problem horizontal scaling.
Comments
Post a Comment