If your application migration strategy involves significant refactoring/re-architecting, what’s the best way to control costs?
Sort By:
Oldest
CIO8 months ago
If significant refactoring/re-architecting is involved then perhaps the best strategy would be to make your application(s) fully utilise cloud-native features and extract the maximum value of choosing cloud e.g. using options like serverless architecture, containerization etc. etc. And in addition, once migrated, deploying cloud FinOps best practices and making use of cloud-native cost monitoring tools (for real-time cost visibility and management). Chief Information and Technology Officer8 months ago
Hi there, at first glance, this would be a suggested approach. 1, Create a future state vision
2, Start with creating an Application Lifecycle Management Program which includes current state, future state and gap analysis
3, Roadmap to get there - some applications can't be migrated or there's no cost benefit to doing that (i.e. applications, services that are only kept for historical purposes). In some cases you can't migrate or doing so would be cost prohibitive and, there are middleware solutions out there to provide the modern look and feel/integration you would like or need. I know of one that works quite well.
Chief Technology Officer and Chief Information Officer8 months ago
It all comes does to estimates. If you know what needs to be done and have skills, then you can at least roughly tell how much efforts it will take. If you don't have the expertise required, you may need assistance from someone who does.Chief Technology Officer in Software8 months ago
The best way is to migrate one component and test it out to validate what you want to achieve is possible. With this , you can extrapolate the timing and cost plus infra requirements. A few systems are born to be monolith and ideally should remain monolith. But yes , microservices has its own advantages.
VP in Finance (non-banking)8 months ago
1. Plan on how are you planning to migrate (in phases or all at once) and also very important to have rollback strategy in phase. It's good to have some sort of flags (which can go back to V1 or V2) so that it can be easily rolled back. That way you don't have to spin new infra (Blue/Green)2. It's good to have a test suite that can test all the product flows with all the re-architecting/refactoring - TDD (Test Driven Development). This can also ensure that the changes being rolled out on prod are well tested and does not break.
3. Also good to have cost monitoring dashboards and alerting to measure the impact.