I agree Node.js is pretty exciting - so much so I wrote a book about
it for Packt Publishing ("Node Web Development")As someone who worked IN the Java SE team at Sun for over 10 years, it was eye opening to see the lengths to which the programming community is going to avoid using XML and Java. I'd think something like Node.js could be done on top of the JVM but because JavaScript has anonymous functions acting like closures as first class objects, and because it's programming style fits closely to the event driven paradigm, JavaScript is a better language for an event driven architecture than Java is. I wrote a blog post a while back going over one big reason for using Node.js - because "real time web" requires an event driven no-threads architecture. Well, I'm not certain about the no-threads part, but the Node.js team points out that threaded architectures have a higher weight than non-threaded event driven architecture. In any case, the blog post went back to some 2006 blog posts that led to the COMET protocol: http://davidherron.com/content/comet-justification-using-nodejs BTW - the Cluster project is another way to load balance Node instances on a single machine. A commenter on one of my blog posts pointed out that the single-thread architecture means Node forces the developer to design in scalability from the beginning of the project. In languages that scale over the threads on a machine, they can scale up to the number of cores on the machine without thinking about scalability. When it comes time to add a second server they have to rethink the architecture. -- You received this message because you are subscribed to the Google Groups "The Java Posse" 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/javaposse?hl=en.
