Book Image

Node.js Design Patterns - Second Edition

By : Joel Purra, Luciano Mammino, Mario Casciaro
Book Image

Node.js Design Patterns - Second Edition

By: Joel Purra, Luciano Mammino, Mario Casciaro

Overview of this book

Node.js is a massively popular software platform that lets you use JavaScript to easily create scalable server-side applications. It allows you to create efficient code, enabling a more sustainable way of writing software made of only one language across the full stack, along with extreme levels of reusability, pragmatism, simplicity, and collaboration. Node.js is revolutionizing the web and the way people and companies create their software. In this book, we will take you on a journey across various ideas and components, and the challenges you would commonly encounter while designing and developing software using the Node.js platform. You will also discover the "Node.js way" of dealing with design and coding decisions. The book kicks off by exploring the basics of Node.js describing it's asynchronous single-threaded architecture and the main design patterns. It then shows you how to master the asynchronous control flow patterns,and the stream component and it culminates into a detailed list of Node.js implementations of the most common design patterns as well as some specific design patterns that are exclusive to the Node.js world.Lastly, it dives into more advanced concepts such as Universal Javascript, and scalability' and it's meant to conclude the journey by giving the reader all the necessary concepts to be able to build an enterprise grade application using Node.js.
Table of Contents (20 chapters)
Node.js Design Patterns - Second Edition
Credits
About the Authors
Acknowledgments
About the Author
Acknowledgments
About the Reviewers
www.PacktPub.com
Preface

Summary


Throughout this chapter, we analyzed some alternative approaches of dealing with asynchronous control flows considering promises, generators, and the upcoming async await syntax.

We learned how to use these approaches to write asynchronous code that is more concise, cleaner and easier to reason about. We discussed some of the most important advantages and drawbacks of these approaches and realized that even if they are very useful they need some time to be mastered. That's why they should not be seen as a complete replacement of callbacks which are still very useful in many scenarios. As a developer, you should now be able to decide which solution best suits the problem you are facing. If you are building a public library that performs asynchronous operations, you should provide an interface that is easy to use, even for developers who only want to use callbacks.

In the next chapter we will explore another fascinating topic relevant to asynchronous code execution and which is another...