Book Image

Mastering Node.js - Second Edition

By : Sandro Pasquali, Kevin Faaborg
Book Image

Mastering Node.js - Second Edition

By: Sandro Pasquali, Kevin Faaborg

Overview of this book

Node.js, a modern development environment that enables developers to write server- and client-side code with JavaScript, thus becoming a popular choice among developers. This book covers the features of Node that are especially helpful to developers creating highly concurrent real-time applications. It takes you on a tour of Node's innovative event non-blocking design, showing you how to build professional applications. This edition has been updated to cover the latest features of Node 9 and ES6. All code examples and demo applications have been completely rewritten using the latest techniques, introducing Promises, functional programming, async/await, and other cutting-edge patterns for writing JavaScript code. Learn how to use microservices to simplify the design and composition of distributed systems. From building serverless cloud functions to native C++ plugins, from chatbots to massively scalable SMS-driven applications, you'll be prepared for building the next generation of distributed software. By the end of this book, you'll be building better Node applications more quickly, with less code and more power, and know how to run them at scale in production environments.
Table of Contents (13 chapters)

Why microservices?

Building larger systems out of smaller, dedicated units is not a new idea. Object-oriented programming follows the same principle. Unix is built this way. Architectures facilitating composable networked software (CORBA, WebObjects, NetBeans) are decades-old ideas. What is new is the scale of profits networked software generates. Customers across nearly every business sector require new software and new features, and software developers are constantly delivering and/or refining those features in response to changing market conditions. Microservices are really a management idea whose goal is to decrease the time it takes to reflect changing business/customer needs in code. The goal is to reduce the cost of change.

As there is no absolute right way to build software, every language design is biased toward one or a few key principles, in particular, principles guiding...