Manning Publications Node.js in Action

helped me a lot!

Heartily recommend this book for anyone that's looking to get into Node JS. It's shame that you can't buy the Kindle version and you have to purchase the book to get a code to download the PDF version.

Libro completo in tutti i suoi aspetti, utile per iniziare a lavorare con nodejs e per capire alcune tematiche ostiche. Assolutamente consigliato.

... completely, what's the reason for the omega plus first web server language / framework system.But let's start from the begin:The book is a very comprehensive, excellent and thorough introduction into Node, Connect and Express. Node is essentially based on the javascript language (but with parts written in C which have to be compiled and installed on the target machine). The author covers- Node and Node libraries basics (incl. the npm Node module network)- DB stuff (not restricted to relational databases but also discussing MongoDB, Mongoose and their concepts, e.g.)- the configurable middleware concept named Connect relying on javascript closure usage providing means to dispatch and chain task execution in a web server- Express web framework with (the usual) concepts for security, templating, skeleton generation, auxiliary functionality, MVC pattern etc.- testing (pointing to different frameworks)- deployment / hosting aspects (whereas Node in itself provides already the / a web server)- furthergoing aspects as provision of TCP/IP servers, cross browser communication via web sockets, CLI tool programming and OS APIs- the Node ecosystem and community support.The examples are formidable and educating.Of some special interest for me were- certain javascript programming techniques- (very elegant) web socket concepts (relying on javascript techniques).Nevertheless, I do not understand completely, why - besides plenty of existing web programming stuff in most different flavours - this additional technique has been introduced. As far as I understood it, the outstanding characteristics are expected to be- event loop programming rather than threading (although parallel work (more or less behind the curtain) is possible, e.g., for parallel file processing in background) with related events resp. callbacks- thereby, a performance gain in comparison with multithreading based systems (comparable to the difference btw. nginx and apache)- unification of client and server programming due to the common javascript basis.Personally, I do prefer rather classical server techniques as Spring or other Java based stuff, even C programming or PHP. There exist plenty of scripting languages as well as web frameworks providing essentially all the introduced features (closures, event handling, MVC, skeleton generation, etc. etc. etc.) as well. Javascript remains for me even for browser programming rather questionable and only famous due to its browser landscape penetration. Why extend it, now, to server programming, too? And even there, as the umpteenth scripting language.

I am a dinosaur from the days of batch processing with Cobol programs on IBM mainframes. I wanted to build a new modern website for the small manufacturing company I now work for. HTML5 and client-side Javascript were fairly easy to pick up, but I had little experience with the server side of things, especially when it comes to interactive versus batch. I was relieved to discover Node.js, which allows server-side programming in Javascript. (I wasn't sure I could handle learning ANOTHER language (like PHP) at this point.) The online documentation for Node.js and its extensions is not (at the time, at least) geared to beginners, so thank goodness for "Node.js in Action." The book is clear and each chapter builds upon the previous one, gradually introducing new abstractions and program sophistication. This book is pretty much a "must have" for programmers new to Node.js, but make sure you have a good grounding in Javascript before you pick it up.