Practical Node.js is your step-by-step guide to learning how to build a wide range of scalable real-world web applications using a professional development toolkit. Node.js is an innovative and highly efficient platform for creating web services. But Node.js doesn't live in a vacuum! In a modern web development, many different components need to be put together -- routing, database driver, ORM, session management, OAuth, HTML template engine, CSS compiler and many more.is the time to discover how to bring it to production level by leveraging its vast ecosystem of packages. As a web developer, you'll work with a varied collection of standards and frameworks -Practical Node.js shows you how all those pieces fit togetherPractical Node.js takes you from installing all the necessary modules to writing full-stack web applications by harnessing the power of the Express.js and Hapi frameworks, the MongoDB database with Mongoskin and Mongoose, Jade and Handlebars template engines, Stylus and LESS CSS languages, OAuth and Everyauth libraries, and the Socket.IO and Derby libraries, and everything in between. The book also covers how to deploy to Heroku and AWS, daemonize apps, and write REST APIs. You'll build full-stack real-world Node.js apps from scratch, and also discover how to write your own Node.js modules and publish them on NPM. You already know what Node.js is; now learn what you can do with it and how far you can take it What you'll learn Manipulate data from the mongo consolelibrarieHapDeploy apps to Heroku and AWSTravisCUtilize sessions for authenticationEveryautclusterit on NP Who this book is for Practical Node.js is for web developers who have some familiarity with the basics of Node.js and want to learn how to use it to build apps in a professional environment. Table of Contents Setting Up Node.js and Other EssentialsUsing Express.js to Create Rapid Node.js Web Apps TDD and BDD for Node.js with MochaTemplate Engines: Jade and Handlebars Persistence with MongoD
Aucun appareil Kindle n'est requis. Téléchargez l'une des applis Kindle gratuites et commencez à lire les livres Kindle sur votre smartphone, tablette ou ordinateur.
Pour obtenir l'appli gratuite, saisissez votre adresse e-mail ou numéro de téléphone mobile.
Commentaires client les plus utiles sur Amazon.com (beta)
42 internautes sur 44 ont trouvé ce commentaire utile
I finally got the way17 novembre 2014
- Publié sur Amazon.com
After going through many books I finally found the best and comprehensive resource to learn the node.js software development. Azat has really done a great work and compiled a great book which really help you in getting complete knowledge about the exciting technology. I read this book and really found it amazing without any doubt. Due to this book my concepts got improved and I started finding the way towards production level software programming. It would have been impossible without the help of this book and that is the reason I am thankful to the author and research team.
11 internautes sur 13 ont trouvé ce commentaire utile
Without a doubt the best Node book available27 juillet 2014
- Publié sur Amazon.com
Without a doubt the best Node book available. At last a writer that makes the effort to ensure the reader experience is a hassle free and learning one. The biggest gripe I have with software development books is the lack of updates. If a book is older than six months none of the examples work and you spend 95% of your time trying to figure out why the code doesn't work. If publishers made sure their books were up to date then this would be a great advantage over piracy. The thing I like about this book is that every step of the way the writer has shown the version of all middleware used to ensure that it works i.e. instead of "npm install -g express-generator" he uses "npm install -g email@example.com". A simple thing that makes a big difference. Writing style is simple and to the point. The examples are great and real World stuff along with little gems thrown in here and there. 10 out of 10 for this! I'll be looking out for his next book!
4 internautes sur 4 ont trouvé ce commentaire utile
Practical Node.js is an essential resource for me24 octobre 2014
- Publié sur Amazon.com
Why I love it:
1) Most chapters features an actual hands-on exercise to perform. Since I’m a kinesthetic learner, which means I learn by DOING, this is the key to making this book work for me. You can try to explain Node to me all you want, and I can take notes on theory, but I need actual written instructions in order to produce tangible results. 2) The book is organized flawlessly. Each chapter builds on the previous so I don’t have to go 0 to 60 without gaining momentum and confidence in a newish (to me) coding language. 3)The book walks you through how to create a few different projects, one of which I have used to jumpstart my own application development. This is probably the biggest benefit of all.
From setting up Node to understanding Mocha to error handling, Practical Node.js has become a fundamental resource in my arsenal.
6 internautes sur 7 ont trouvé ce commentaire utile
More code than instruction22 novembre 2014
- Publié sur Amazon.com
The author is definitely very well versed in Node.js, but the book is more code than instruction & explanation (mostly uncommented code nonetheless). It shows good examples of how the author would implement very specific projects, but you need to be very capable of reading code in order to really understand how everything works together in order to apply it to your scenario.
12 internautes sur 16 ont trouvé ce commentaire utile
endless listings with comments which state the obvious15 octobre 2014
- Publié sur Amazon.com
I'm a control theory engineer with 20 years of professional experience in enterprise level software development. It is entirely my fault that I bought the book strictly based on its 5.0 average out of 12 reviews. Must be authors friends. And now... Author says: 'Figure 4-4 shows how the home page looks after adding style sheets'...Yes, maybe, but not until after adding menu.jade in includes, and after doing lots of additional changes in controller/model i.e. app.js (which is not done until two chapters later), and after you start 'mongod' process, and after you add some articles and... and counting. The matter of the fact is that you cannot see the results of your .jade views without the model which in turn draws information from the persistence layer - but author doesn't find it worth mentioning. He simply states: 'Figure 4-4 shows how the home page looks after adding style sheets.' Isn't that just great? Regarding this, the approach to form the views first and then everything else is a bit strange - at least for a book. I've never seen it in my professional career. This lone example illustrates the whole 'organization' of the book. Chaotic, unstructured with tons of pages wasted on listings of the code from the source file which is available anyway. Sometimes twice - as a listing and then 'full listing'. To make things worse, such listings are not accompanied by explanations, nuances, advices, best practices... he never draws readers attention to important details or pitfalls. Most of the time the author just says: 'The full code of xxxxx.xxx file is as follows', or for the variation's sake: 'Now we can look at the home page template index.jade that extends layout' which is nothing more but stating the obvious. Having said that, there are some useful advices when installing and setting up frameworks/libraries.
I also can't understand why author ruthlessly lists all the features of countless libraries he chooses to cover (why so many alternatives in the first place?). Most of the features he doesn't explain or, in a very rear occasion 'explains' in a wrong way. Take for instance the essential Node's module property: 'module.exports' and 'exports'. Instead of explaining the real difference (which is by the way very simple, but still important), he conveys disinformation: 'sometimes it's more fitting to invoke a constructor... In this case, module.exports is needed'. Unbelievable! Author simply doesn't seem to fundamentally know the stuff he writes about, or he doesn't care.
The English language used is really basic and sometimes with the odd order of words in the sentence. This makes it hard for the author to explain the subtleties or transmit the essence. Try to compare it with the expressiveness of Ethan Brown or Michael S. Mikowski/Josh C. Powell who authored books on exactly the same subject. What a difference! Don't get me wrong, I found easily every answer to my questions in the original documentation of each library/framework author covers, and within two days I deciphered the book - but was I supposed to? Just for the sake of curiosity, I took a look at couple of other author's books. They all use the same almost-trivial projects which source codes author lists relentlessly all the way through. My conclusion is that the author wrote couple of simple applications and then exploited every single line of code to contribute to the number of pages and number of books which he published under different names with different publishers (which still could have been okay if he analyzed the snippets properly).
The book is 'void'. Avoid void! (Douglas Crockford).