TL;DR: In this article we will see how easy it is to load balance dockerized Node.js applications with NGINX. We will create a simple Node.js application that serves an HTML file, containerize it with Docker, and containerize an NGINX instance that uses round-robin algorithm to load balance between two running instances of this application.

Docker is a software container platform. Developers use Docker to eliminate “works on my machine” problem when collaborating with co-workers. This is done by putting pieces of a software architecture on containers (a.k.a. dockerize or containerize).

This is the sixth chapter of the Writing a JavaScript framework series. In this chapter, I am going to discuss the usefulness of Custom Elements and their possible role in a modern front-end framework's core.

The series is about an open-source client-side framework, called NX. During the series, I explain the main difficulties I had to overcome while writing the framework. If you are interested in NX please visit the home page.

The series includes the following chapters:

Components took over the web in the recent years. All of the modern front-end frameworks - like React, Vue or Polymer - utilize component based modularization. They provide distinct APIs and work differently under the hood, but they all share the following features with many of the other recent frameworks.

Then let’s go back to our top level custom NGINX directory;

cd /opt/custom_nginx/nginx-1.10.3/

Then let’s build our package. This might take a while. If you get a question during installation on whether to “Use the available Release binaries?”, just say Y.

sudo dpkg-buildpackage -b

When the build is finished we go up a level to our top level custom_nginx folder;

cd /opt/custom_nginx

There should be several NGINX debian packages in this folder now.
Let’s install our custom full version (choose the version that matches your Ubuntu version);

sudo dpkg --install nginx-full_1.10.3-0+xenial0_amd64.deb

That’s it! Our custom NGINX build is now installed.