Take away after a cloud migration project

Before starting the project

Keep the applications and databases loosely coupled.

Get the applications up to date in terms of dependent libraries.

Do not create or remove cross database query

Keep the applications to be standard and consistent throughout the team / company.

Decommission unused systems constantly

 

Create a task to do

Draw the line between lift-and-shift and migration.

Do not change how it works or where it is hosted if there is no benefit to it.

Minimize the core task so that migration to be as simple as possible.

Do not mix a migration task with an improvement work.

 

Dry run

Do a dry run the release day tasks, which will bring up some unexpected surprises.

 

On the day of application

Create a to-do list of items that needs to be done with a rough time table.

Consider the dependencies of tasks.

Prioritize the tasks. Low priority tasks does not need to be done in the release day.

Put a name next to each task so that everyone involved knows what to do.

Leave a comment

Your email address will not be published. Required fields are marked *