General Technologies

Let’s start with a brief history of the evolution of application deployment. Traditional Application Deployment Era: In the traditional environment, organizations used to run applications on physical servers. There was no way to define resource boundaries in a physical server and this caused resource allocation problems. For example, if multiple applications ran on a physical server, there were instances where one application would take up most of the resources, and as a result, the other applications would underperform. A solution for this was to run each application on a different physical server. But this had a problem- it gave rise to many physical servers that were not scalable. As a result, resources were underutilized, and it was expensive for organizations to maintain many  physical servers . This problem gave rise to a solution: Traditional Virtual Machines. Figure 1: Traditional Architecture vs Virtual Architecture Virtualization Era:  Virtu...

In contrast to traditional applications where all components are developed in one piece, some types of applications become easier to build and maintain when they are broken down into smaller pieces that work synchronously. Applications that are built as modular components are easier to understand, test and maintain. Naturally, this makes your organization more agile. Organizations can benefit from time reduction, scalability, and resilience. So, what are  Linux Containers ? Linux Containers are a set of one or more processes that are isolated from the rest of the system. Simply put, Containers are software packaging applications that isolate only those components that are needed for its operation. Containers encapsulate software/service, application, all of its dependencies and a minimal amount of runtime applications that it needs to perform its function. Linux Containers  are therefore very similar to traditional Virtual Machines. But then, How are Linux...