- Paperback: 300 pages
- Publisher: Apress; 1 edition (July 11, 2014)
- Language: English
- ISBN-10: 1430265957
- ISBN-13: 978-1430265955
- Product Dimensions: 7 x 0.7 x 10 inches
- Shipping Weight: 1.4 pounds (View shipping rates and policies)
- Average Customer Review: 137 customer reviews
- Amazon Best Sellers Rank: #897,671 in Books (See Top 100 in Books)
Enter your mobile number or email address below and we'll send you a link to download the free Kindle App. Then you can start reading Kindle books on your smartphone, tablet, or computer - no Kindle device required.
To get the free app, enter your mobile phone number.
Practical Node.js: Building Real-World Scalable Web Apps 1st Edition
Use the Amazon App to scan ISBNs and compare prices.
There is a newer edition of this item:
Frequently bought together
Customers who bought this item also bought
About the Author
Try the Kindle edition and experience these great reading features:
Read reviews that mention
There was a problem filtering reviews right now. Please try again later.
- The author (Azat Mardan) knows the MEAN stack very well. He seems to have some real-world experience with these technologies.
- Azat's experience with the MEAN stack has given him some insight about them. I have tried several of the relative technologies to the MEAN stack like different template engines (Jade, Handlebars, EJS, ...), different Express middleware, different database solutions/session stores (mongoDB, Redis, ...). I can say that Azat's recommendations about which of these technologies you should consider in various developement scenarios are spot on. To me, what he recommends and his choice of complementary technologies for your Node.js/MEAN projects are excellent recommendations. In my own experience, I ended up trying different options and ended up choosing pretty much the same technologies recommended in this book. Like I said, I have read other books on Node.js/MEAN and this is not always the case.
- The book directs you towards different resources for further reading/exploring of subjects covered in the book or not covered but worth knowing about.
Now, what makes this book imperfect is mainly that it seems to have lacked careful editorial reviewing before being put on the market. There are some holes here and there when you read the book. This has been mentioned by other reviewers. This is a little frustrating but in my case it happened maybe 2 or 3 times during my reading. I was reading and then suddenly : "Hey, how did we get to this code from the last code example ?". It seems like the author has jumped or omitted some transitional paragraphs here and there. But we have to keep in mind that this is a book about some fast-changing open-source technologies and the author has to get it out quickly, otherwise it becomes outdated by the time it gets published. And as far as I know, when this book came out on the market, there was pretty much nothing else that covered as much of these topics. So it was still highly valuable, even with its imperfections.
I have not mentioned the topics of mongoDB and angularJS in my review because I have learned these from other sources. I have read these chapters quickly but I can say that if you're serious about using these technologies in your stack, you will need to complement the info provided in this book with some more in-depth books/online tutorials/... Again, Azat Mardan shares some good insights about how to use these in your projects, whether you should use mongoskin or mongoose with mongoDB, etc. But these topics simply have too much scope to be covered extensively in this book.
Overall, I think that this book is still valuable today. It has certainly help me. We keep an eye on the io.js project that seems promising but it's not ready for production yet. So at this point in time, Node.js and the MEAN stack is a great option for some projects and this book will get you started fast. My recommendation is that you buy this book and one or two other books on the MEAN stack at the same time. This has worked well for me because you can compare the different approaches from the authors. You can also read on a single topic across your 2-3 books and some info will be complementary. With books like this one and others on open-source tech, spreading your reading between different books helps you gain a better perspective on the topics.
It is fun to read book with printed links like: "[...]", seriously, which is actually an article from this writer. Endless and pointless listings with no, or short explanations.
It feels just like few tutorials from averange web page were glued together and printed out. As a digital tutorial thats ok, as a printed book - Im feeling sad for a wasted trees.
The layout is ugly, scattered, poorly organized, and generally distracting. The material jumps from subject to subject almost haphazardly. As I'm reading it, I often wonder why the author even bothered to include many sections or why I should care about what was just presented to me. It feels like a collection of loosely related blog posts that respond to questions that nobody ever asked. Possibly this is the left-over parts of other books that just never got used. As soon as one subject is briefly touched upon, the author stops and moves on to the next thing, usually another framework or other technology.
Worse, this book is more expensive than lots of other Node.js books that offer greater depth.
If you want a whirlwind tour of ways you might be able to add new technologies to your Node.js applications, this book might be for you, but if you want any kind of in-depth information about Node.js itself, I would avoid this book.
The other book, the one you will read, is full of typos and incomplete thoughts, so that following along can be a significant challenge. In a way you could view this as a positive, because it forces you to dig deeper into the online documentation to repair the text as you read, fortifying your knowledge even more. Then because of the many precedents for mistakes, there are an equal number of spots that I mistook for mistakes, but were in fact accurate. All these 'parsing errors' result in some lost efficiency.
Overall, it seems to me that these technologies are moving so fast that a snapshot such as this, while blurry, may be a trade off between clarity and relevance. While I wish it was a little more carefully proofread, I'd still say it offers a considerable amount of insight into the tools in its scope.
I strongly believe that Node is the best framework for the web, and this books does a great job introducing you to this amazing technology. Obviously, it doesn't cover ALL about Node, it's to wide a subject to be fit in this book.
I like a lot that the author walks you step by step through all the steps and technology that you require to put forward a well made web application.
As a seasoned developer, I recommend this book to everyone that wants to learn Node, it is usefull for beginners and experts (I'm an expert and found very interesting things in this book), I totally recommend it!