Cloud Migration Strategy for AWS & Azure: 6 Common Techniques

hello and welcome back in this lecture we are going to learn how to recognize and explain the six hours or the six common strategies used when discussing cloud migration projects in 2011 Gartner group outlined five common migration strategies which provided a great benchmark for discussing and defining migration strategy in the early days of public cloud adoption over the fullness of time that has evolved into six definitions which we are commonly used when discussing migration to cloud services they're commonly called the six R's and they are re hosts re platform repurchase refactor retain and retire let's work through these six strategies so we are clear on the operational benefits and the business merit of each construct just before we start let's just reaffirm that every migration is going to be unique and that these strategies are not meant to be definitive or mutually exclusive they should be used as guidelines and discussion starters only something that can be very helpful when you are running a cloud transformation workshop or a brainstorming session and as we will see with the expertise pls migration project a migration project can easily include elements of all of these strategies at various stages so first cab off the rank is Rijos commonly referred to as lift and shift now lift and shift is generally as it sounds lifting servers or applications from the current hosting environment and shifting them to infrastructure in the public cloud we hosting and lift and shift is a very common strategy for organizations starting out on their migration journey there are significant benefits in running servers on the scalable pay-as-you-go infrastructure of a public cloud platform so it is a relatively low resistance migration strategy and this is a great strategy for working backward from a fixed constraint or a hard deadline in practice the application or server will be exported via a third-party export tool like VMware vCenter for example or created as an image that can be exported to a compute instance or container run on a cloud compute service containerized applications make this process a relatively simple exercise as the operating environment isn't included in the container steamer if you are running our monolithic application then this Rijo sling can again be a simple way of getting started with cloud services second cab off the rank is reap platforming which is to modify lift and shift brief platforming involves making some optimizations to the application during the migration stage so the third R is to repurchase which is sometimes referred to as drop end shop and this refers to their decision to move to another product this may mean ending existing licensing and repurposing services on a new platform or service examples of this may be a CRM system or an industry specific application not designed to run on cloud infrastructures now this is often not necessary with bespoke applications written with modern application code as with modern code it is possible to transport the code from one provider to another the repurchase strategy is often applied when using a proprietary data based platform or proprietary product our fourth R is refactoring or rerp tating and this strategy is usually driven by a strong desire to improve services drivers for this might be that it is difficult to make improvements in the current environment or it may be a requirement to improve availability and reliability immediately say to meet a specific security or compliance requirement with refactoring much depends on the nature of the service you want to refactor if it is not a mission-critical service then it may be possible to re-architect the service as required during the migration stage refactoring is feasible during the first phase of a migration if you do not have a time constraint otherwise it is most likely better done at a later phase of the project okay so strategy number five is to retain you may want to retain portions of your IT portfolio because there are some applications that you are not ready to migrate and feel more comfortable keeping them on premise with this use case it may make sense to retain aspects of your IT services in their current environment and implement a hybrid or part migration strategy so this approach makes sense if current regulatory or constitutional rules require you to store or run some aspects of your services or business application on-premise or within specific regions so that brings us to strategy number six which is to retire services now this strategy involves identifying assets and services that can be turned off so the business can focus on services that are widely used and on immediate value to the business so that brings us to the end about brief summary of the six common migration strategies

Channel: Cloud Academy

Views: 43,019

Rating: 4.8620691 out of 5

Keywords: AWS, cloud computing, cloud migration, IT, technology, cloud migration strategies, learn cloud, migrating to aws, amazon web services, cloud migration strategy, cloud migration projects, rehost, refactor, revise, rebuild, replace, gartner 5 r's

Id: AmyuEIux6xs

Length: 4min 59sec (299 seconds)

Published: Tue Feb 27 2018