How to Start With Container Using Docker

A layman’s introduction to why you would want a container:

Let’s say you need to build an application. That can be next Facebook, next Pandora, next Amazon, next Youtube, or whatever. To make that application to be available to the public, you need some place to host it. Previously, that means you need to build your own computer and to setup a dedicated web service called “server,” which is basically a computer dedicated for hosting website or web service instead for your own person computer, or put that application onto hosting company like 1&1, GoDaddy.com, Geocity, etc.

Then, the age of “cloud” came in. A company like Amazon became very good at putting your application through their own “data center,” which is a bunch of collections of servers. Unlike web hosting service, these companies adopted a concept called “virtualization,” meaning that the hardware resources can be broken down even further through software functionality and provide resources more optimally to customers who need them. This is why “cloud computing” is known as “utility computing”, since you only pay for the services you use, instead of taking the entire server for your own use. This is generally more cost efficient for both yourself and for the hosting company, not to mention it is more optimized for performance.