428
edits
Changes
mLine 261:
Line 261: − cloud - some optimization of resources should occur to keep costs low. Turn off, used reserved instances. + − '''Replatform'''+ − Address EOL software driven by the ITPINs+ − Move to platforms (PaaS) avoid OSes, serverless, lifecycle management+ − Containers+ − + − + + + + +
no edit summary
'''Rehost (lift and shift)'''
'''Rehost (lift and shift)'''
With a rehost migration strategy, the application undergoes no changes and is migrated as-is to a new data centre or cloud. This is the simplest and least effort migration strategy.
For workloads migrating to cloud, it is strongly advised that, at the very least, the resources (network, compute, storage) be optimized and reduced to the smallest size possible. Additionally using reserved instances for production workloads and turning off unused servers during off-hours will help ensure a lower monthly bill from your cloud provider.
'''Replatform (lift, shift, and tinker)'''
With a replatform strategy, the application undergoes minor changes as it is migrated to a new data centre or cloud. Replatforming strategies may include, but as not limited to:
Addressing end of life (EOL) software such as those deprecated by IT Policy Implementation Notice [https://www.canada.ca/en/treasury-board-secretariat/services/information-technology/policy-implementation-notices.html ITPINs]
'''Refactor'''
Move to Platform-as-a-Service (PaaS). For commoditized services such as databases, web servers, file servers, container orchestration, moving to a PaaS allows for a serverless architecture. A serverless architecture negates the need to manage and patch operating systems, middleware and manage server instances. This also reduces an organization's IT LifeCycle Management burden. Users sometimes worry that using PaaS will cause vendor lock-in. By using PaaS that have alternatives elsewhere in the market will avoid lock-in. Being able to extract your business data and business rules from a PaaS is key to avoiding lock-in. Most cloud providers offer database, web server, and file server platforms. While migrating from one to another may not be completely painless, migration tools and APIs exist to allow for this possibility.
Make elastic.
Containers is an increasingly populate method to deploy applications. If your application is stateless, moving it to a container will not only help portability, but also help with your organization's adoption of DevOps practices.
'''Refactor (Re-Architect)'''
With a refactoring Make elastic.
Function as a service.
Function as a service.