An organization plans to shift its internal portal from local hosting to a new environment and intends to adopt a managed data solution. The team is ready to modify the data-related components but wants to keep most of the existing system unchanged. Which approach is most appropriate?
Replatform suits a situation where the original code base is preserved while introducing modifications for a new service, such as a managed data solution. Rehost is mainly a lift-and-shift with no changes, which would not satisfy the goal of adapting the data-related components. Re-architect constitutes a major overhaul, exceeding the level of change the team wishes to undertake. Retire removes the portal from use, which is not the plan.
Ask Bash
Bash is our AI bot, trained to help you pass your exam. AI Generated Content may display inaccurate information, always double-check anything important.
What is the main difference between replatforming and rehosting?
Open an interactive chat with Bash
Why isn't re-architecting the best choice in this scenario?
Open an interactive chat with Bash
What are some examples of managed data solutions that could apply in replatforming?