Book Image

Node.js Web Development - Third Edition

By : David Herron
Book Image

Node.js Web Development - Third Edition

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.

Related Content you might be interested in

Current Title:

Small book image
Node.js Web Development - Third Edition
David Herron
Jun, 2016 | 376 pages
No titles found
Table of Contents (18 chapters)
Node.js Web Development Third Edition
Node.js Web Development Third Edition
Credits
Credits
About the Author
About the Author
About the Reviewer
About the Reviewer
www.PacktPub.com
www.PacktPub.com
Preface
Preface
Free Chapter
1
About Node.js
About Node.js
The capabilities of Node.js
Why should you use Node.js?
Summary
2
Setting up Node.js
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
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
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
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
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
Data Storage and Retrieval
Data storage and asynchronous code
Logging
Storing notes in the filesystem
Summary
8
Multiuser Authentication the Microservice Way
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
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
Deploying Node.js Applications
Notes application architecture
Traditional Linux Node.js service deployment
Node.js microservice deployment with Docker
Summary
11
Unit Testing
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

Introducing Socket.IO

The aim of Socket.IO is:

To make real time apps possible in every browser and mobile device.

It supports several transport protocols, choosing the best one for the specific browser.

If you were to implement your application with WebSocket, it would be limited to the modern browsers supporting that protocol. Because Socket.IO falls back on so many alternate protocols (WebSockets, Flash, XHR, and JSONP), it supports a wide range of web browsers, including some old crufty browsers. Older Socket.IO versions claimed to support back to Internet Explore 5.5, but that claim is no longer printed on their website.

As the application author, you don't have to worry about the specific protocol Socket.IO uses in a given browser. Instead, you can implement the business logic and the library takes care of the details for you.

Socket.IO requires that a client library make its way into the browser. That library is provided, and it is easy to instantiate. You'll be writing code on both the...

Previous Section
End of Section 2
Next Section