...

• High resource overhead
• Slow startup
• DevOps nightmare (High maintenance cost (DevOps operation costs like installing / patching / maintaining many OS and applications)
• Murky Devs Development and DevOps boundaries -   "Works on my machine" problemproblems

Container Approach

The main difference between container deployments seen in the industry is the orchestration (i.e. what is responsible for starting and stopping the containers amongst other tasks). The jtel container stack uses docker compose.

...

• Lightweight - low resource overhead
• Much higher density per host
• Fast startup in seconds or lessDevOps greatly simplified - the same container runs on a dev laptop or in production reducing environment specific bugs
• Maintenance like Updates, smaller patches or migrations streamlined and efficient
• Fast Desaster recovery (The complete stack can be built from the ground up in minutes, depending mostly on the database size for speed of deployment) 
• Clean Devs / DevOps Boundary

...

• A new vanilla (empty) installation
• Migrating from an existing old school installation to a container installation
• Migrating from one container stack to another stack hosted somewhere else
  • Change IaaS providers
  • Out of place updates
• Disaster recovery from the nightly daily backup

This means, that we effectively test disaster recovery every time a stack is deployed or updated. 

...