Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Methodology/Strategy/Focus

TIS is a medium sized application with many developers working on it at any particular time. It also has downstream dependencies which we don’t control but may influence. With this in mind, we should try to adhere to the following principles.

Developer Flow

Whatever we do, we must bring the rest of the team with us by keeping them “in the know”. We’ll also need to make as little change to the environments and applications as possible. This is so that if anything happens, developers will not need to do anything “special” or at least they would know what they’d need to do to achieve what they need to in the new environment.

Seamless

The migration should be completely seamless to a user. While browsing on TIS while on Azure, should look and feel no different to when it is deployed on AWS.

Downstream dependencies such as the NDW and GMC should also have no impact.

The work

We currently see a number parts of this migration work. This consists of:

...