Node.js Design Patterns: Master best practices to build modular and scalable server-side web applications, 2nd Edition 2nd ed. Edition

Hi All! I am sure that this content is 5 stars and someday I will update my review to 5 stars. Why 1 star today? Since I have to tell you smth really important. I bought 1st edition, I love it, I bought second edition, I like it, and I hope that I will buy 3rd edition and I will love it again. For the first edition I fired critical errata, that limmited parallel spiders will never work for nesting bigger than 1 (2 or 3 etc.). I fired clear explanation why final callback will never be fired. Packt told me that this errata will take longer to understand and in a mean time here is promo code to get any book for free. I don't need any book for free, I want to pay your guys and I want this "Nodejs Design Patterns" book to become better, since this is the best book for you to get nodejs essentials. Also lots of mistakes exists in code snippets, but non of them in 1st edition. For example combine streams code snippet. First edition is with correct one, second is missing comma. Juniors developers can't catch such things.So I wish to Mario and Luciano good luck with 3rd edition. And I am sure I will buy it.

If you buy this book because you are seeking some design patterns, this book has that, but it doesn't treat it as the primary topic throughout the book and it seems to only remember to discuss it a little bit in each chapter or two. Rather, this book encompasses more than just Node.js design patterns and covers topics involving callbacks, Promises, generators, isomorphic JavaScript, React, modules, ECMAScript 2015, streams, architecture, and much more. All of the topics are important, no doubt, but should all of those topics go into a book that uses "Design Patterns" as its title? I think not, and so I took away a star. Either re-word the title of the book or remove the chapters that are more along the lines of general topics in Node.js / JavaScript and perhaps place those in their own book. Don't get me wrong. I read all chapters of the book and from each chapter, I learned something, so I don't consider the book to be uninformative. However, I think that the title of a technical book should reflect what it primarily discusses within. Maybe other reviewers will disagree and say that I'm being too picky, but if wanted to read about isomorphic JavaScript or React, I would buy a book on those subjects and not have the money paid for a "design patterns" book to cover them regardless of how well-intentioned the authors may have treated the subject. Having said all of that, if you are a serious Node.js developer, this is a well done book overall regardless of the title and I would recommend it to you.

I would think of myself an intermediate developer on client side JavaScript and newbie on the server side. This book was exactly what I needed. It's well structured, informative, and saved me hours of going through blogposts and gather fragmented information without full context.I'm several chapters in and I'm really liking it.

skills to the next level. I was at an intermediate level not sure where to go next and this was the answer! I think (no offense) that whoever said that this is not as design pattern specific as the name implies does not actually understand what the term design patterns really means or must have a different definition for it that I don't know of. I completely disagree with you. In almost every chapter there is a design pattern being discussed. I can't get tired of reading this book! I would highly recommend it.

This book came very highly recommended to me by all the best Node developers I know. After reading it I must concur. This is the book you want to help take your Node skills to the next level. I've read most of the serious Node books on the market, and this one is the best I've read.

I just finished reading through this book. It feels like it doesn't take full advantage of the ES6 as it could, but nonetheless it was still an effective and enjoyable read. The patterns described are detailed in a thorough, intuitive manner which makes it easy for the reader to retain and understand.The only minor gripe I have about this book is the lack of editing. There are a handful of grammar, spelling, and code syntax mistakes that although not difficult to mentally correct, do take you out of "the flow." Hopefully the publisher gets enough errata submissions to publish a more polished version.That being said, it is definitely not a reason to skip this book. If you are a Node developer, the information and ideas presented in this book are invaluable. Give it a go!

This is a must, got alot out of this book regarding internals and real world examples.Every chapter is great, I enoyed each. You wont be sorry for your purchase.

I bought this book to start learn more about the NodeJS ecosystem. It is helpful.