Sign In Start Free Trial

Book Overview & Buying
Table Of Contents

Node.js Web Development - Third Edition

By : David Herron

4.1 (18)

Node.js Web Development

4.1 (18)

By: David Herron

Overview of this book

Node.js is a server-side JavaScript platform using an event driven, non-blocking I/O model allowing users to build fast and scalable data-intensive applications running in real time. Node.js Web Development shows JavaScript is not just for browser-side applications. It can be used for server-side web application development, real-time applications, microservices, and much more. This book gives you an excellent starting point, bringing you straight to the heart of developing web applications with Node.js. You will progress from a rudimentary knowledge of JavaScript and server-side development to being able to create and maintain your own Node.js application. With this book you'll learn how to use the HTTP Server and Client objects, data storage with both SQL and MongoDB databases, real-time applications with Socket.IO, mobile-first theming with Bootstrap, microservice deployment with Docker, authenticating against third-party services using OAuth, and much more.

Preface

Preface

What this book covers

What you need for this book

Who this book is for

Conventions

Reader feedback

Customer support

Free Chapter

1. About Node.js

1. About Node.js

The capabilities of Node.js

Why should you use Node.js?

Summary

2. Setting up Node.js

2. Setting up Node.js

System requirements

Installing Node.js using package managers

Installing from source on POSIX-like systems

Installing developer tools on Mac OS X

Node.js versions policy and what to use

Running and testing commands

NPM – the Node.js package manager

Node.js and ECMAScript 6 (ES-2015, ES-2016, and so on)

Summary

3. Node.js Modules

3. Node.js Modules

Defining a module

Node.js's algorithm for require (module)

npm – the Node.js package management system

A quick note about CommonJS

Summary

4. HTTP Servers and Clients – A Web Application's First Steps

4. HTTP Servers and Clients – A Web Application's First Steps

Sending and receiving events with EventEmitters

HTTP server applications

ES-2015 multiline and template strings

HTTP Sniffer – listening to the HTTP conversation

Web application frameworks

Getting started with Express

Calculating the Fibonacci sequence with an Express application

Making HTTP Client requests

Calling a REST backend service from an Express application

Summary

5. Your First Express Application

5. Your First Express Application

ES-2015 Promises and Express router functions

Express and the MVC paradigm

Creating the Notes application

Theming your Express application

Scaling up – running multiple Notes instances

Summary

6. Implementing the Mobile-First Paradigm

6. Implementing the Mobile-First Paradigm

Problem – the Notes app isn't mobile friendly

Mobile-first paradigm

Using Twitter Bootstrap on the Notes application

Mobile-first design for the Notes application

Building a customized Bootstrap

Summary

7. Data Storage and Retrieval

7. Data Storage and Retrieval

Data storage and asynchronous code

Logging

Storing notes in the filesystem

Summary

8. Multiuser Authentication the Microservice Way

8. Multiuser Authentication the Microservice Way

Creating a user information microservice

The Notes application stack

Summary

9. Dynamic Interaction between Client and Server with Socket.IO

9. Dynamic Interaction between Client and Server with Socket.IO

Introducing Socket.IO

Initializing Socket.IO with Express

Real time updates on the Notes home page

Inter-user chat and commenting for Notes

Summary

10. Deploying Node.js Applications

10. Deploying Node.js Applications

Notes application architecture

Traditional Linux Node.js service deployment

Node.js microservice deployment with Docker

Summary

11. Unit Testing

11. Unit Testing

Testing asynchronous code

Assert – the simplest testing methodology

Testing a model

Using Docker to manage test database servers

Testing REST backend services

Frontend headless browser testing with CasperJS

Summary

Index

Index

Node.js's algorithm for require (module)

In Node.js, modules are either stored in a single file, as discussed previously, or as a directory with particular characteristics. There are several ways to specify module names and several ways to organize module deployment in the filesystem. It's quite flexible, especially when used with the npm package management system for Node.js.

Module identifiers and path names

Generally speaking, the module name is a pathname but with the file extension removed. Earlier, when we wrote require('./simple'), Node.js knew to add .js to the filename and load in simple.js.

Modules whose filenames end in .js are of course expected to be written in JavaScript. Node.js also supports binary code native libraries as Node.js modules, whose filename extension is .node. It's outside the scope of this book to discuss implementation of native code Node.js modules. This gives you enough knowledge to recognize them when you come across one.

Some Node...

Visually different images

CONTINUE READING

83

Tech Concepts

36

Programming languages

73

Tech Tools

Unlimited access to the largest independent learning library in tech of over 8,000 expert-authored tech books and videos.

Innovative learning tools, including AI book assistants, code context explainers, and text-to-speech.

50+ new titles added per month and exclusive early access to books as they are being written.

Node.js Web Development

Search

Your notes and bookmarks