This week's book giveaways are in the Java EE and JavaScript forums.
We're giving away four copies each of The Java EE 7 Tutorial Volume 1 or Volume 2(winners choice) and jQuery UI in Action and have the authors on-line!
See this thread and this one for details.
The moose likes HTML, CSS and JavaScript and the fly likes Better Understanding of Node.js Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login


Win a copy of The Java EE 7 Tutorial Volume 1 or Volume 2 this week in the Java EE forum
or jQuery UI in Action in the JavaScript forum!
JavaRanch » Java Forums » Engineering » HTML, CSS and JavaScript
Bookmark "Better Understanding of Node.js" Watch "Better Understanding of Node.js" New topic
Author

Better Understanding of Node.js

Gregg Bolinger
GenRocket Founder
Ranch Hand

Joined: Jul 11, 2001
Posts: 15299
    
    6

Can anyone explain to me any problems that Node.js solves and where its use makes the most sense? The majority of people I talk to about this always default to "because I can write the code in JavaScript". I don't care about that, to be perfectly honest. I care about what problems Node.js solves.


GenRocket - Experts at Building Test Data
Rob Crowther
author
Ranch Hand

Joined: Nov 06, 2012
Posts: 295
    
    5

The problem it's solving for the people you talk to is having to write the server side of an application in a different language to the client side. If you only want to know what problems it solves that you care about you will have to first tell us which problems you care about.


Read my books: Hello! HTML5 & CSS3 | HTML5 in Action | Read my blog
Gregg Bolinger
GenRocket Founder
Ranch Hand

Joined: Jul 11, 2001
Posts: 15299
    
    6

Thanks Rob. I just want more than "I can write javascript". Surely the whole non-blocking IO callback event driven nature of Node.JS is meant to solve a specific set of server side pitfalls. I just don't know exactly what those are. I guess a better question is, what is a good use case for node over the typical / standard existing stacks.

Node is good when you have to ________________________ .
Bear Bibeault
Author and ninkuma
Marshal

Joined: Jan 10, 2002
Posts: 61066
    
  66

Gregg Bolinger wrote:Node is good when you have to ________________________ .


I love the idea of Node.js, and I'm sure at some time I may have a way to fill in that blank, but for now, I haven't found it.

My backends these days are almost exclusively RESTful APIs, and I'm mostly using the Play framework (v.1) to create them.


[Asking smart questions] [Bear's FrontMan] [About Bear] [Books by Bear]
Rob Crowther
author
Ranch Hand

Joined: Nov 06, 2012
Posts: 295
    
    5

Node is basically a lightweight networking framework, its main appeal over similarly capable frameworks and/or app servers (eg. Twisted in Python or, more debatably, nginx as a server) is that the native scripting language is JavaScript. With careful planning, you only write your model and business logic once and then can use most of it interchangeably on both sides. While there is a large amount of 'next big thing' hype surrounding Node which is, in many ways, unwarranted, what that means from a practical perspective is that there's a vibrant community of people writing plugins and frameworks for it, and it's easy to get help and advice.
 
I agree. Here's the link: http://aspose.com/file-tools
 
subject: Better Understanding of Node.js