Knowledgebase

Planning a Move to Containers Print

  • 0

Doing it deliberately.

WHAT TO ESTABLISH FIRST

What problem you are solving.

WHAT GOOD ANSWERS LOOK LIKE

Environments that differ and cause failures Deployment that is slow or risky Onboarding that takes days Difficulty running several versions

WHAT POOR ANSWERS LOOK LIKE

It is what everyone uses It will make us scalable

WHY THAT SECOND ONE FAILS

Containers do not make an application able to run as several instances.

WHAT ORDER TO WORK IN

Containerise one application Run it in one environment Establish the build pipeline Move non-production environments Move production Consider orchestration only afterwards

WHY THAT ORDER

Each step delivers value and teaches what the next requires.

WHAT TO CHOOSE FIRST

An application that is important enough to matter and simple enough to succeed.

WHAT NOT TO CHOOSE FIRST

The most complex system you have Anything stateful

WHAT TO EXPECT

Configuration and state problems, not packaging problems.

WHAT TO BUDGET FOR

Learning, and the first few painful deployments.

WHAT TO ESTABLISH BEFORE PRODUCTION

Monitoring Backups A documented rollback

WHAT TO MEASURE

Whether deployment actually improved.


Was this answer helpful?
Back

Are you happy with your experience? Leave us a review on Trustpilot.


Trustpilot