Containerization | Manual Deployment

Tools to start over lovely bare metal strong 💪 hardware:

• Master Brain: Kubernetes

• Containerization Runtime (Wrapper around deployable package): Docker (mini-vm for saving costs no more, don't over-think it) to construct an up and running a container

• Runtime: Which will contain the deployable package that will be an executable later and will be able to serve requests upon being healthy available

• Deployable package: This part is variable over time

  • the Senior System admin [Linux Based] will need to move this one from his/her local laptop after building the latest package locally from the SCM server using specific commands and the final outcome will be a docker image, then
  • he/she has to move this image to the testing environment where Kubernetes resides 😜 then
  • run the container from this image in a healthy available state

---

Runtime of developed applications:

• Backend (Java, Spring-Boot): JRE

• Web Frontend (JavaScript, React): Nodejs

• Mobile Frontend (Java, Android SDK): JRE

---

Hints upon Docker usage in different environments:

• Use base image wisely (based on less size and effectiveness like reviews and its robustness in different environments) when writing Dockerfile, because it affects on the image building time AKA transmitting fucken bloody hell a lot of packets over the network

• Read a bit in image layers to optimize the image as much as you can (less layers is better)