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

Static files and CDNs

We are currently using Express' static app to serve our JavaScript and CSS. A best practice for scalable sites is to push any static content onto a Content Delivery Network (CDN). If you have ever used Facebook (they do have a pretty large user base), you have used a CDN. If you inspect your Facebook profile, you will see a domain come up again and again, fbstatic-a.akamaihd.net. This is the CDN that Facebook uses for static assets. A CDN will have multiple servers across the world with the same content. Based on where the request comes from, the CDN will return the closest source. We are going to do something similar with this application using Amazon Simple Storage Service (S3).

Note

Some of you out there might say S3 is not a CDN, and you are correct. Amazon has CloudFront to do this. S3 will be better than serving static assets with Node.js, and until an application grows beyond a certain size and scope, S3 will fill the need of a CDN.

Creating an S3 bucket

We create...