Rehost, replatform, refactor, replace, retire
On This Lesson 4 topics
This lesson is planned. The outline below lists the topics it will cover. The full lesson has not been published yet.
In this lesson
know the disposition options and when each fits.
Planned topics
- Rehost: move as is to new infrastructure; quick, little benefit beyond hosting.
- Replatform: small changes to use managed services; moderate effort and benefit.
- Refactor or re-architect: change the code and structure to gain agility or scale; high effort.
- Replace: swap for a packaged product or SaaS; retire: switch off; retain: keep as is for now.
- Names vary by source; use one set consistently.
Draft outline details
Demonstration
a Larkspur table: application, option, reason. Web shop: replace; reporting: replatform; ERP: retain; an old store-labelling tool: retire.
Check your understanding
When is rehosting a poor choice?
Show answer
When the reason for moving is a design problem that hosting will not fix.
Practice
Apply this lesson with the module's lab, exercises and quiz.
Marking a lesson complete is optional and you can undo it any time. Your progress stays in this browser.