What not to do
We’ve shown what is to be done, so let’s see what shouldn’t or mustn’t be done. These are the common pitfalls and anti-patterns – the things that may seem obvious and perfectly acceptable but that nevertheless aren’t.
Here are some anti-patterns to avoid (in random order):
- Accumulating technical debt without justification and a plan to address it – this is never a good idea anyway, but it is especially bad if the cloud adoption is trying to address and improve the time-to-market. Remember, if you are building it or you’ve built it and it isn’t in the hands of your customers, what good did any of that effort do?
- Lift-and-shift with no modernization plans – the cloud wasn’t meant for this, except in a very narrow case of maintenance and no further development until the service gets decommissioned. That is the only acceptable case of lift-and-shift.
- Assessing the skills available...