Cloud repatriation - When does it make sense for you?
summary
IDC finds 50% considering repatriation and only two thirds of cloud projects stay on or under budget. Examples include a Windows Server 2008 VM moved to Azure for extended support then returned on-prem for performance, and multiple region outages causing 2–4 hour business disruptions. Migration paths use Terraform or CloudFormation and VM conversion tools; options are colocation, private/hybrid cloud, edge, or orchestration layers like VMware, Nutanix and OpenShift for multi-cloud control.
AI-written summary · about
chapters (11)
- 0:00Intro
- 1:41CLOUD ADOPTION TRENDS
- 10:14PERFORMANCE
- 13:28SECURITY & GOVERNANCE
- 15:53SKILLS & CAPABILITIES GAP
- 18:07WHEN TO PULL THE TRIGGER? STRATEGIC
- 19:11COST BENEFIT ANALYSIS
- 20:17QUESTIONS TO CONSIDER
- 21:10MOVE BACK TO DATA CENTER
- 22:18MOVE TO NON-PUBLIC CLOUD
- 27:09CLOUD REPATRIATION SHOULD BE PART OF YOUR CLOUD STRATEGY PLAYBOOK
related talks
26mWhen the Cloud s Reign is Over
49mWhat to look out for when migrating your data to the cloud; is it REALLY the right choice?
46mEverything you need to know about cloud migration
25mMigrate Your Enterprise Applications to the Cloud
29mJourney through the center of migrations
31mOn-Prem is the new Black
36mMigrate to the cloud in mere months? No problem!
56mNavigating the Cloud as a Cloud Architect