Note

Nix

Meaning of container sharing same resource

Introduction

Sometimes we have to pick up a project from where the previous devs have left it or work on previous code base. So we must know how to work with that and adapt. Instead of cloning the repo, fork them.

Any full stack website will have 3 things:

• The frontend site
• The backend app
• The database

Make sure you setup all these things properly to get started.

<aside> 💡 Analyze the previous codebase properly and instead of completely critisizing the code try to understand it.

</aside>

Bare Metal VS Virtual Machine VS Containers

Serverless and Edge Computing

Containers and History

A container is a way to package applications with everything they need inside of the package, including the dependencies and all the configuration necessary.

• Technically container is made up of images.
• We have layers of stacked images on top of each other and at the base of most of the containers, you would have a Linux based image, which is either Alpina or some other Linux distribution.
• Usually there are some intermediate images that will lead up to the actual application image(from alphine to app) that is going to run in the container. And of course, on top of that, you will have all this configuration data.

An interesting thing is that there is still no strict definition of “containers”. Even virtual machines can be called "containers" when they provide container-like interfaces, e.g., when they implement the OCI (Open Container Initiative) specs.