Building Scalable Apps with Redis and Node.js

Book Image

Building Scalable Apps with Redis and Node.js

By : Joshua Johanan

Book Image

Building Scalable Apps with Redis and Node.js

By: Joshua Johanan

Overview of this book

Building Scalable Apps with Redis and Node.js

Building Scalable Apps with Redis and Node.js

Credits

About the Author

About the Author

About the Reviewers

About the Reviewers

www.PacktPub.com

www.PacktPub.com

Preface

Free Chapter

Backend Development with Express

Backend Development with Express

Node.js and Node Package Manager

Using Express in Node

Using middleware in Express

Adding templates to the mix

Using sessions in Express

Processing forms

Very simple authentication

Setting up a config file for our app

Methods to extend an application

Extending Our Development with Socket.IO

Extending Our Development with Socket.IO

Node package versions

Building a simple Socket.IO app

Broadcasting a message

Using the disconnect event

Creating namespaces

Using namespaces or rooms

Using namespaces and rooms together

Using Socket.IO and Express together

Adding application-specific events

Using Redis as the store for Socket.IO

Socket.IO inner workings

Ideas to take away from this chapter

Authenticating Users

Authenticating Users

Node package versions

Let's build our authentication

Registering a Facebook application

Using Passport to authenticate to Facebook

Using Google for authentication

Adding Google authentication to our application

Adding more OAuth providers

Adding secure local authentication

Password-storing theory

RabbitMQ for Message Queuing

RabbitMQ for Message Queuing

Node package versions

Getting RabbitMQ

Our first message queue

Sending messages back

Adding message queues to PacktChat

Message queuing in RabbitMQ

Adopting Redis for Application Data

Adopting Redis for Application Data

Node package versions

Installing Redis

Using Redis data structures

Redis persistence

Using Redis as a message queue

Adding Redis to PacktChat

Redis is for application state

Using Bower to Manage Our Frontend Dependencies

Using Bower to Manage Our Frontend Dependencies

Node package versions

Installing and using Bower

Introducing React

Introducing Backbone

Using Backbone and React for DOM Events

Using Backbone and React for DOM Events

Bower package versions

Finishing Socket.IO

Creating React components

Backbone models

The Backbone router

Putting it all together

Updating CSS and the layout

Adding a new worker

Trying out our application

JavaScript Best Practices for Application Development

JavaScript Best Practices for Application Development

Node package versions

Setting up tests

Setting up different environments

Introducing Grunt

Static files and CDNs

Scripting our new tools

Deployment and Scalability

Deployment and Scalability

Creating servers on EC2

What is Ansible?

Debugging and Troubleshooting

Debugging and Troubleshooting

Using Chrome Developer Tools

Inspecting requests

CPU profiling our application

Taking heap snapshots

Index

Customer Reviews

5 star

0

4 star

0

3 star

0

2 star

0

1 star

0

Scalability

We have automated the rolling out of our code to servers in the cloud, but how is this scalable? The first thing we take a look at is a diagram of how our application looks:

The front public-facing address of our site will be the server that is running HAProxy. In this setup, we will only want one server running HAProxy, and if it is production, this site should have a static IP and a public DNS record. HAProxy is very efficient at load balancing, and one of them can handle a lot of traffic. Eventually, we can run two behind a balanced DNS record, for example, but this is out the scope of this book.

HAProxy will then send the requests to one of our application servers behind it. These servers do not need a public-facing DNS record. They only need to communicate with the HAProxy server (and technically our computer so that SSH/Ansible will work). Each one of these servers will only be running one instance of Node and our application. We could even configure Ansible to kick off multiple...