Book Image

The Node Craftsman Book

By : Manuel Kiessling
Book Image

The Node Craftsman Book

By: Manuel Kiessling

Overview of this book

The Node Craftsman Book helps JavaScript programmers with basic Node.js knowledge to now thoroughly master Node.js and JavaScript. This book dives you deeper into the craft of software development with Node.js and JavaScript, incuding object-orientation, test-driven development, database handling, web frameworks, and much more. The Node Craftsman Book shows you how to work with Node.js and how to think deeply about how you build your Node projects. You'll master how to build a complete Node.js application across six crafting milestones, and you'll learn many specific skills to achieve that mastery. These skills include how to work with the Node Package Manager in depth, how to connect your Node applications to databases, and how to write unit tests and end-to-end tests for your code. You'll experience the full Node.js development picture, and learn how to craft and control your Node.js applications - right through to fully-fledged web applications using REST, and integration with Angular applications.
Table of Contents (17 chapters)
Free Chapter
1
Part 1: Node.js Basics in Detail
2
Working with NPM and Packages
3
Test-driven Node.js Development
11
Milestone 1 – A First Passing Test Against the Server
13
Milestone 3 – Setting the Stage for a Continuous Delivery Workflow

Optimizing Code Performance and Control Flow Management Using the Async Library

Writing or using functions or methods in your code that are executed one after the other gets you a long way in your applications.

Sometimes, those functions are simple synchronous steps:

console.log('Starting calculation...');
var result = 5 + 4; 
console.log('The result is', result);

Often, callbacks are used when operations are executed in the background and jump back into our code's control flow asynchronously at a later point in time:

console.log('Starting calculation...');
startExpensiveCalculation(5, 4, function(err, result) { 
  if (!err) { 
    console.log('The result is', result);
  }
});

If those asynchronous background operations bring forth a more complex callback behaviour, they might be implemented as an event emitter:

console.log('Starting calculation...');

calculation...