On 04.07.2014 14:58, Adam Davies wrote:
Seems like the state of the art is to stick with Java services on the
backend and use Node as a page server to server HTML pages content, so
that Node is a kind of front-controller or proxy.
In a way. Node can do a lot of work and it can handle a whole lot of
connections, as well as route all those connections between Java
services, databases and other stuff.
The thing where it is not the best match is heavy-duty processing. So,
if you're serving images or have a webshop or something that connects to
many different warehouses to pull data from, Node is great. If you're
doing video encoding and recoding, then yep, leave that part to Java.
--
Zlatko
--
Job board: http://jobs.nodejs.org/
New group rules:
https://gist.github.com/othiym23/9886289#file-moderation-policy-md
Old group rules:
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 unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/nodejs/53B714D8.4090608%40gmail.com.
For more options, visit https://groups.google.com/d/optout.
