Important cloud migration terms - Google Cloud Platform Tutorial

- [Instructor] You'll hear some common terminology when learning about modernizing infrastructure and applications in the cloud. Let's introduce or remind you of some of these terms. The first is workload. In cloud computing, a workload is a specific application, service, or capability that can be run in the cloud or on-premises. Workloads include: containers, databases, and virtual machines. Sometimes workloads get retired. Retiring a workload means removing it from a platform. A workload might be retired because it's unnecessary, not cost-effective, secure, or compatible with a specific platform. Alternatively, workloads are often retained. Retaining a workload means that it's intentionally kept. When a workload is retained, it's typically kept on-premises or in a hybrid cloud environment. This means that the workload will continue to be managed by the business and will not be subject to the same level of cloud provider control. Many workloads are rehosted. In cloud computing, rehost refers to the migration of a workload to the cloud without changing anything in the workload's code or architecture. This is often done as a first step in cloud migration because it's the simplest and quickest way to run a workload in the cloud. This process is often referred to as lift and shift. However, rehosting also has some drawbacks, including: it doesn't use all the benefits of cloud computing, managing workloads that were rehosted without making any changes can be difficult, and scaling workloads that were rehosted without making any changes can also be difficult. Then, there's replatform. In cloud computing, replatform refers to the process of migrating a workload to the cloud while making some changes to the workload's code or architecture. This process is often called move and improve. Replatforming lets organizations: benefit from the cloud's scalability, reliability, and cost-effectiveness, improve the performance of their workloads, and reduce the cost of their workloads. However, replatforming also has some drawbacks, including: it can be a complex and time-consuming process, making the necessary changes to the workload's code or architecture can be difficult, and testing the changes to the workload's code or architecture can also be difficult. Sometimes, workloads are refactored, which refers to the process of changing the code of a workload. For example, an organization might refactor a workload to use either a cloud-based microservices architecture or a cloud-based serverless architecture. We'll explore what those concepts mean later in this course. Refactoring has some benefits. It means that workloads can become more efficient, scalable, or secure and a valuable investment for organizations that want to use all cloud capabilities. That being said, a possible drawback for organizations is that refactoring a workload can be a complex and time-consuming process. And finally, cloud modernization can inspire and incentivize organizations to reimagine. In cloud computing, reimagine refers to the process of rethinking how an organization uses technology to achieve its business goals. This can involve reconsidering the organization's current cloud strategy and its use of other technologies, such as artificial intelligence and machine learning. Reimagining cloud computing can help organizations to: improve their efficiency, reduce costs, and increase agility. It can also help organizations better meet the needs of their customers and partners.