6 R’s of Migration

Reference

6 R’s strategies

  • Rehosting
    • Lift and shift
    • This is completely our responsibility as cloud engineers.
    • Responsibilities:
      • 100 % ownership
  • Replatforming
    • Lift, tinker and shift
    • Responsibilities:
      • Migration => 100 % ownership
      • Replatforming
        • You might do it, if its related to OS, kerner versions etc
        • If it is with code changes, then we test them
  • Repurchasing
    • I will not be migrating but i will purchase some other product in cloud which does exactly what by product does.
    • Responsibilities:
      • POC (Proof of Concepts) / Pilot
  • Refactor/Re-architecturing
    • Developers redesign and then we host the application.
    • Responsibilities:
      • Create DevOps Pipeline for newly architected application to cloud
      • If necessary, you will be doing ETL (Extract, Transform & Load)
  • Retire
    • Get rid of this
  • Retain
    • You have decided not to migrate at this moment

Preview

By continuous learner

devops & cloud enthusiastic learner

Leave a Reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.

Please turn AdBlock off
Floating Social Media Icons by Acurax Wordpress Designers

Discover more from Direct DevOps from Quality Thought

Subscribe now to keep reading and get access to the full archive.

Continue reading

Visit Us On FacebookVisit Us On LinkedinVisit Us On Youtube