Chances are that your APPLICATION already has a framework for shipping logs and backing up data to the right places at the right times. To implement Docker, you not only need to REPLICATE the logging behavior you expect in your virtual machine environment, but you also need to prepare your compliance or governance team for these changes.

New tools are ENTERING the Docker space all the time, but many do not match the STABILITY and maturity of existing solutions. Partial updates, rollbacks and other COMMON deployment tasks may need to be reengineered to accommodate a containerized deployment.

If it’s not broken, don’t fix it. If you’ve already invested the engineering time required to build a continuous integration/continuous delivery (CI/CD) pipeline, containerizing legacy apps may not be worth the time investment.

Chances are that your application already has a framework for shipping logs and backing up data to the right places at the right times. To implement Docker, you not only need to replicate the logging behavior you expect in your virtual machine environment, but you also need to prepare your compliance or governance team for these changes.

New tools are entering the Docker space all the time, but many do not match the stability and maturity of existing solutions. Partial updates, rollbacks and other common deployment tasks may need to be reengineered to accommodate a containerized deployment.

If it’s not broken, don’t fix it. If you’ve already invested the engineering time required to build a continuous integration/continuous delivery (CI/CD) pipeline, containerizing legacy apps may not be worth the time investment.