Edit Question - KnowledgeHub

Title Body

Let's say I'm building a 3-tier web site, with Mongo DB on the back end and some really lightweight javascript in the browser (let's say just validation on forms, maybe a couple of fancy controls which fire off some AJAX requests). I need to choose a technology for the 'middle' tier (we could segment this into sub-tiers but that detail isn't the focus here, just the overall technology choice), where I want to crunch some raw data coming out of the DB, and render this into some HTML which I push to the browser. A fairly typical thin-client web architecture. My safe choice would be to just implement this middle tier in Java, using some libraries like Jongo to talk to the Mongo DB and maybe Jackson to marshal/unmarshal JSON to talk to my fancy controls when they make AJAX requests. And some Java templating framework for rendering my HTML on the server. However, I'm really intrigued by the idea of throwing all this out the window and using Node.js for this middle tier, for the following reasons: I like javascript (the good parts), and let's say for this application's business logic it would be more expressive than Java. It's javascript everywhere. No need to switch between languages, and indeed the OO and functional paradigms, when working anywhere on the stack. There's no translation plumbing between the tiers, JSON is supported natively everywhere. I can reuse validation logic on the client and server. If in the future I decide to do the HTML rendering client-side in the browser, I can reuse the existing templates with something like Backbone with a pretty minimal refactoring / retesting effort. If you're at this point and like Node, all the above will seem obvious. So I should choose Node right? BUT... this is where it falls down for me: as we all know Node is based around a single-threaded async I/O web server model. This is great for my scalabilit

Tags (comma-separated) Cancel