...
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. tldr minimise hacks and keep things as close to what they are now.
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.
To infinity and beyond
Any work done for the migration should have some thought to migrating towards “The moon on a stick”. So any solution should make it easier and not harder
The work
We currently see a number parts of this migration work. This consists of:
...