您现在访问的是微软AZURE全球版技术文档网站,若需要访问由世纪互联运营的MICROSOFT AZURE中国区技术文档网站,请访问 https://docs.azure.cn.

云合理化Cloud rationalization

云合理化是评估资产以确定在云中迁移或现代化每个资产的最佳方式的过程。Cloud rationalization is the process of evaluating assets to determine the best way to migrate or modernize each asset in the cloud. 有关合理化过程的详细信息,请参阅 什么是数字领域?For more information about the process of rationalization, see What is a digital estate?.

合理化上下文Rationalization context

本文中所列 合理化的五大合理化 是一种很好的方法,用于标记被视为云候选项的任何工作负荷的可能未来状态。The five Rs of rationalization listed in this article are a great way to label a potential future state for any workload that's being considered as a cloud candidate. 在您尝试合理化环境之前,应将此标记过程置于正确的上下文中。This labeling process should be put into the correct context before you attempt to rationalize an environment. 查看以下误解以提供该上下文:Review the following myths to provide that context:

误区:在此过程初期做出合理决策Myth: It's easy to make rationalization decisions early in the process

准确合理化需要深入了解工作负荷和相关资产 (应用程序、基础结构和数据) 。Accurate rationalization requires a deep knowledge of the workload and associated assets (applications, infrastructure, and data). 最重要的是,准确的合理化决策需要一些时间。Most importantly, accurate rationalization decisions take time. 建议使用 增量合理化过程We recommend using an incremental rationalization process.

误区:云采用必须等待所有工作负荷都合理化Myth: Cloud adoption has to wait for all workloads to be rationalized

合理化整个 IT 资产组合甚至单个数据中心,都可以按月甚至数年延迟业务价值的实现。Rationalizing an entire IT portfolio or even a single datacenter can delay the realization of business value by months or even years. 如果可能,应尽可能避免完全合理化。Full rationalization should be avoided when possible. 而是使用 10 种方法的强大功能发布规划 ,以对未来10个工作负荷进行明智的决策,这些工作负荷是为云采用而记录的。Instead, use the Power of 10 approach to release planning to make wise decisions about the next 10 workloads that are slated for cloud adoption.

误区:业务理由必须等待所有工作负荷都合理化Myth: Business justification has to wait for all workloads to be rationalized

若要为云采用工作制定业务理由,请在项目组合级别进行一些基本假设。To develop a business justification for a cloud adoption effort, make a few basic assumptions at the portfolio level. 当动机与创新保持一致时,假设示意图。When motivations are aligned to innovation, assume rearchitecture. 当动机与迁移保持一致时,假定 rehost。When motivations are aligned to migration, assume rehost. 这些假设可以加快业务理由。These assumptions can accelerate the business justification process. 然后,在每个工作负荷的采用周期的评估阶段,将对假定和预算进行细化。Assumptions are then challenged and budgets refined during the assessment phase of each workload's adoption cycle.

现在,请查看以下 5 Rs 的合理化,以便熟悉长期过程。Now review the following five Rs of rationalization to familiarize yourself with the long-term process. 开发云采用计划时,请选择最适合你的动机、业务成果和当前状态环境的选项。While developing your cloud adoption plan, choose the option that best aligns with your motivations, business outcomes, and current state environment. 数字空间合理化的目标是设置基准,而不是对每个工作负荷进行合理化。The goal in digital estate rationalization is to set a baseline, not to rationalize every workload.

合理化的 5 个 RThe five Rs of rationalization

此处列出的五大合理化的 5 Rs 介绍了最常见的合理化选项。The five Rs of rationalization that are listed here describe the most common options for rationalization.

重新托管Rehost

这也称为 提升和 迁移迁移,rehost 工作将当前的状态资产移至所选的云提供商,同时对整体体系结构进行最小的更改。Also known as a lift and shift migration, a rehost effort moves a current state asset to the chosen cloud provider, with minimal change to overall architecture.

常见的驱动程序可能包括:Common drivers might include:

  • 降低资本支出。Reducing capital expense.
  • 释放数据中心空间。Freeing up datacenter space.
  • 在云中实现快速投资回报。Achieving rapid return on investment in the cloud.

量化分析因素:Quantitative analysis factors:

  • VM 大小 (CPU、内存、存储) 。VM size (CPU, memory, storage).
  • (网络流量) 的依赖关系。Dependencies (network traffic).
  • 资产兼容性。Asset compatibility.

质化分析因素:Qualitative analysis factors:

  • 更改的容差。Tolerance for change.
  • 业务优先级。Business priorities.
  • 关键业务事件。Critical business events.
  • 处理依赖关系。Process dependencies.

重构Refactor

平台即服务 (PaaS) 选项可降低与许多应用程序相关联的运营成本。Platform as a service (PaaS) options can reduce the operational costs that are associated with many applications. 最好略微重构应用程序以适应基于 PaaS 的模型。It's a good idea to slightly refactor an application to fit a PaaS-based model.

"重构" 也指重构代码的应用程序开发过程,使应用程序能够实现新的业务机会。"Refactor" also refers to the application development process of refactoring code to enable an application to deliver on new business opportunities.

常见的驱动程序可能包括:Common drivers might include:

  • 更新过程速度更快且时间更短。Faster and shorter updates.
  • 代码的可移植性。Code portability.
  • 更高的云效率 (资源、速度、成本) 管理的操作。Greater cloud efficiency (resources, speed, cost, managed operations).

量化分析因素:Quantitative analysis factors:

  • 应用程序资产大小 (CPU、内存、存储) 。Application asset size (CPU, memory, storage).
  • (网络流量) 的依赖关系。Dependencies (network traffic).
  • 用户流量 (页面视图、页面上的时间、加载时间) 。User traffic (page views, time on page, load time).
  • 开发平台 (语言,数据平台,中间层服务) 。Development platform (languages, data platform, middle-tier services).
  • 数据库 (CPU、内存、存储) 版本。Database (CPU, memory, storage, version).

质化分析因素:Qualitative analysis factors:

  • 继续业务投资。Continued business investments.
  • 突发选项或时间线。Bursting options or timelines.
  • 业务流程依赖关系。Business process dependencies.

重新架构Rearchitect

由于在构建应用程序时进行了体系结构决策,某些老化应用程序与云提供程序不兼容。Some aging applications aren't compatible with cloud providers because of the architectural decisions that were made when the application was built. 在这些情况下,应用程序可能需要在转换之前重建。In these cases, the application might need to be rearchitected before transformation.

在其他情况下,与云兼容的应用程序(而不是云本机),可通过将解决方案重新架构到云本机应用程序中来提高成本效益和运营效率。In other cases, applications that are cloud-compatible, but not cloud-native, might create cost efficiencies and operational efficiencies by rearchitecting the solution into a cloud-native application.

常见的驱动程序可能包括:Common drivers might include:

  • 应用程序规模和灵活性。Application scale and agility.
  • 更易于采用新的云功能。Easier adoption of new cloud capabilities.
  • 混合技术堆栈。Mix of technology stacks.

量化分析因素:Quantitative analysis factors:

  • 应用程序资产大小 (CPU、内存、存储) 。Application asset size (CPU, memory, storage).
  • (网络流量) 的依赖关系。Dependencies (network traffic).
  • 用户流量 (页面视图、页面上的时间、加载时间) 。User traffic (page views, time on page, load time).
  • 开发平台 (语言,数据平台,中间层服务) 。Development platform (languages, data platform, middle tier services).
  • 数据库 (CPU、内存、存储) 版本。Database (CPU, memory, storage, version).

质化分析因素:Qualitative analysis factors:

  • 不断增长的业务投资。Growing business investments.
  • 操作成本。Operational costs.
  • 潜在反馈循环和 DevOps 投资。Potential feedback loops and DevOps investments.

重新生成Rebuild

在某些情况下,必须克服的增量可能会太大,无法进一步增加投资。In some scenarios, the delta that must be overcome to carry an application forward can be too large to justify further investment. 对于以前满足业务需要但目前不受支持或未对齐当前业务流程的应用程序,尤其如此。This is especially true for applications that previously met the needs of a business but are now unsupported or misaligned with the current business processes. 在这种情况下,将创建一个新的基本代码,以便与 云本机 方法保持一致。In this case, a new code base is created to align with a cloud-native approach.

常见的驱动程序可能包括:Common drivers might include:

  • 加快创新。Accelerating innovation.
  • 更快地生成应用程序。Building applications faster.
  • 降低运营成本。Reducing operational cost.

量化分析因素:Quantitative analysis factors:

  • 应用程序资产大小 (CPU、内存、存储) 。Application asset size (CPU, memory, storage).
  • (网络流量) 的依赖关系。Dependencies (network traffic).
  • 用户流量 (页面视图、页面上的时间、加载时间) 。User traffic (page views, time on page, load time).
  • 开发平台 (语言,数据平台,中间层服务) 。Development platform (languages, data platform, middle tier services).
  • 数据库 (CPU、内存、存储) 版本。Database (CPU, memory, storage, version).

质化分析因素:Qualitative analysis factors:

  • 降低最终用户的满意度。Declining end-user satisfaction.
  • 受功能限制的业务流程。Business processes limited by functionality.
  • 潜在的成本、经验或收入收益。Potential cost, experience, or revenue gains.

ReplaceReplace

通常使用最佳的技术和方法实现解决方案。Solutions are typically implemented by using the best technology and approach available at the time. 有时,软件即服务 (SaaS) 应用程序可以为所承载的应用程序提供所有必需的功能。Sometimes software as a service (SaaS) applications can provide all the necessary functionality for the hosted application. 在这些情况下,可以计划工作负荷以供将来替换,从而有效地将其从转换工作量中删除。In these scenarios, a workload can be scheduled for future replacement, effectively removing it from the transformation effort.

常见的驱动程序可能包括:Common drivers might include:

  • 围绕行业最佳实践进行标准化。Standardizing around industry best practices.
  • 加速采用业务流程驱动的方法。Accelerating adoption of business-process-driven approaches.
  • 将开发投资重新分配给创建竞争优势或优点的应用程序。Reallocating development investments into applications that create competitive differentiation or advantages.

量化分析因素:Quantitative analysis factors:

  • 一般的操作成本降低。General operating-cost reductions.
  • VM 大小 (CPU、内存、存储) 。VM size (CPU, memory, storage).
  • (网络流量) 的依赖关系。Dependencies (network traffic).
  • 要停用的资产。Assets to be retired.
  • 数据库 (CPU、内存、存储) 版本。Database (CPU, memory, storage, version).

质化分析因素:Qualitative analysis factors:

  • 当前体系结构与 SaaS 解决方案的成本效益分析。Cost benefit analysis of the current architecture versus a SaaS solution.
  • 业务流程地图。Business process maps.
  • 数据架构。Data schemas.
  • 自定义或自动化过程。Custom or automated processes.

后续步骤Next steps

您可以将这 5 Rs 的合理化应用于数字领域,以帮助您做出有关每个应用程序未来状态的合理决策。Collectively, you can apply these five Rs of rationalization to a digital estate to help you make rationalization decisions about the future state of each application.