This Post Has 13 Comments

1. Very well written. Took my code to another level.
   This is a really good book. If you use NodeJS, I would highly suggest it. Especially if you’re not already a senior developer. It introduced me new concepts but it really helped me get my code more organized and strategic through using proven design patterns .The author, Luciano is VERY good with NodeJS and is really a top tier developer and great teacher!We’ll worth the small price!!!

   Reply

2. Node.js reference
   Thanks amazon for delivering the book in perfect condition.The authors have done a great job of putting together a rich source of technical information for Node.js developers.

   Reply

3. Professional level, well written
   This book is amazing, in depth and super informative. If you really into nodejs you have to grab this book as soon as possible.The only complain I have is that the book is not loosely coupled. Every chapter is building on the previous one, which I find unnecessary. For example the last chapter, Messaging techniques shouldn’t be coupled with the rest of the book.

   Reply

4. Muy buen libro para aprender de temas avanzados.
   Te enseña temas avanzados de Node.js y de programación en general. Los patrones de diseño se pueden utilizar en otros lenguajes por que este libro te enseña las bases para no estancarte en un solo lenguaje o framework.

   Reply

5. Clean and well structured
   This book gets straight to the point, and there are many practical examples.You can find fundamentals and more advanced notions.Each chapter is well designed and the presentation of topics follows a well-structured logic.

   Reply

6. Deep knowledge about Node.ja
   I found this book very useful and knowledgeable. Great and clean up to date content.You can either read it by order or use it as a reference.Love it.Thank you

   Reply

7. Deep dive into Node.js, JavaScript style
   An excellent book that covers many topics, including design patterns, with every example in JavaScript. The author does a great job of explaining each subject with multiple examples refactoring each into the optimal solution.

   Reply

8. What contents were very good. Amazon Customer Service was predictively bad.
   The contents of the book were very informative and helped me understand the technology to a new level as well as being well written.However, the book itself was received damage and, after calling Amazon Customer Service, I was promised a monetary credit for the damage book from Amazon, at least at first.Several weeks went by and I never received any monetary credit from Amazon for the damaged book. So I called Amazon Customer Service again and they said they had no record of me being promised any monetary compensation for the damaged book. It appears as if the quality of Amazon Customer Service has taken a step backwards. All three books in this order were damaged so at least Amazon Customer Service is consistent in one regard – when they damage something they damage it thoroughly.

   Reply

9. I am liking the book, it explains a lot of low level concepts of nodejs and the part of design patterns shows great exemples how to use the pattern explained, instead of just theory.Worth the purchase. I really recommend.

   Reply

10. Well Twitter. Worth the money

    Reply

11. Un libro strutturato veramente bene, con esempi chiari e precisi, mirati a spiegare i concetti esposti. Molto completo ed ampio tratta praticamente tutti gli aspetti e gli approcci di node.Great job for Mario and Luciano

    Reply

12. Libro que siempre recomiendo a los desarrolladores junior o a los que quieran mejorar sus habilidades con Node. Bien estructurado y con el contenido necesario para entender como trabajar de forma profesional con este lenguaje.

    Reply

13. If you are a serious Node developer (or hope to be), you must read this book. That’s all there is to it.First off, the book’s title seriously _undersells_ this book. It covers way, _way_ more than design patterns.Now, given how central Node is to ALL JavaScript development workflows these days (ie. anyone using Webpack/React, etc.), I’d strongly suggest anyone who writes JS in any serious way should read this book. For Node devs, again, it’s a must. I had read the 2nd edition, and even so this 3rd edition was worth the read (they’ve updated everything for ES6, reorganized, and added a bunch of new material).The authors start at the fundamentals of how Node itself works (single thread, non-blocking I/O, etc.), then take a bottom-up approach to teach you not just Node, but the very fundamentals of asynchronous JS coding – going into great detail on each of the 4 core pillars of async JS code (events, callbacks, promises, and async/await).They completely explain the JS Module systems used in Node, explaining both CommonJS and ES6 modules, as well as the key similarities/differences of how they are loaded and execute at runtime (or bundle-time), where each type can/can’t be used, how to use each type in Node, and so on.Even tho most Node devs may not use Streams much, this book does a whole chapter in fantastic detail to explain how they work, why they are so central to Node, and why that’s such a strength of the platform. Of course they then explain a variety of example uses/patterns built on Streams, to drive the points home.The rest of the book is mostly design patterns from there. Each pattern is well explained, with ample example code and diagrams to clarify all you need to know. You may know all of them already (unlikely), but even if you do there are tips and tricks you can pick up along the way.Lastly, the final chapter is a rewrite (as I recall) of their prior coverage of messaging patterns, completely updated to reflect the growth and prominence of microservices. They give 75 pages to cover all the essential messaging patterns you’ll probably need, and include numerous really solid (tho not prod-ready) examples using ZeroMQ, RabbitMQ, and even Redis Streams (which could apply to Kafka, etc. conceptually as well).OK, I’ll stop gushing. I’ll just close to say that coming in at over 600 pages, this book is a commitment, for sure. Once you start reading it, though, it flies by (I read it in a week). The writing is clear, the diagrams and code examples are great, and the value is self-evident.Buy it. Read it. Thank me later. …You’re welcome. 😉

    Reply