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

云采用框架企业级设计原则Cloud Adoption Framework enterprise-scale design principles

本指南中规定的企业规模体系结构基于此处所述的设计原则。The enterprise-scale architecture prescribed in this guidance is based on the design principles described here. 这些原则可作为整个关键技术领域中后续设计决策的指南。These principles serve as a compass for subsequent design decisions across critical technical domains. 你应熟悉这些原则,以便更好地理解它们的影响以及与不遵守这些原则相关的权衡。Familiarize yourself with these principles to better understand their impact and the trade-offs associated with nonadherence.

订阅大众化Subscription democratization

订阅应用作管理单元,并根据业务需求和优先级调整,以支持业务领域和项目组合所有者,加速应用程序迁移和新的应用程序开发。Subscriptions should be used as a unit of management and scale aligned with business needs and priorities to support business areas and portfolio owners to accelerate application migrations and new application development. 应向业务部门提供订阅,以支持设计、开发和测试新的工作负荷以及迁移工作负荷。Subscriptions should be provided to business units to support the design, development, and testing of new workloads and migration of workloads.

策略驱动的治理Policy-driven governance

Azure 策略应该用于提供 guardrails,并确保与组织的平台以及部署到其上的应用程序保持持续的符合性。Azure Policy should be used to provide guardrails and ensure continued compliance with your organization's platform, along with the applications deployed onto it. Azure 策略还为应用程序所有者提供充足的自由,并为云提供安全的受阻碍路径。Azure Policy also provides application owners with sufficient freedom and a secure unhindered path to the cloud.

单个控件和管理平面Single control and management plane

企业规模的架构不应考虑任何抽象层,如客户开发的门户或工具。Enterprise-scale architecture shouldn't consider any abstraction layers, such as customer-developed portals or tooling. 它应该为 AppOps(集中管理的操作团队)和 DevOps(专用应用程序操作团队)提供一致的体验。It should provide a consistent experience for both AppOps (centrally managed operation teams) and DevOps (dedicated application operation teams). Azure 在所有 Azure 资源和预配通道(受基于角色的访问和策略驱动的控制的约束)中提供统一且一致的控制平面。Azure provides a unified and consistent control plane across all Azure resources and provisioning channels subject to role-based access and policy-driven controls. 可使用 Azure 建立一组标准化的策略和控制措施,以管理整个企业资产。Azure can be used to establish a standardized set of policies and controls for governing the entire enterprise estate.

以应用程序为中心和原型中立Application-centric and archetype-neutral

企业规模体系结构应该侧重于以应用程序为中心的迁移和开发,而不是纯基础结构直接迁移,例如移动虚拟机。Enterprise-scale architecture should focus on application-centric migrations and development rather than pure infrastructure lift-and-shift migrations, such as moving virtual machines. 它不应区分新旧应用程序、基础结构即服务或平台即服务应用程序。It shouldn't differentiate between old and new applications, infrastructure as a service, or platform as a service applications. 最终,它应该为要部署到 Azure 平台的所有应用程序类型提供安全可靠的基础。Ultimately, it should provide a safe and secure foundation for all application types to be deployed onto your Azure platform.

协调 Azure 本机设计和路线图Align Azure-native design and roadmaps

企业级体系结构方法支持尽可能使用 Azure 本机平台服务和功能。The enterprise-scale architecture approach advocates using Azure-native platform services and capabilities whenever possible. 此方法应与 Azure 平台路线图一致,以确保新功能在你的环境中可用。This approach should align with Azure platform roadmaps to ensure that new capabilities are available within your environments. Azure 平台路线图应有助于通知迁移策略和企业级轨迹。Azure platform roadmaps should help to inform the migration strategy and enterprise-scale trajectory.

建议Recommendations

请准备好权衡功能,因为第一天不太可能需要所有内容。Be prepared to trade off functionality because it's unlikely that everything will be required on day one. 使用预览版服务并依赖服务路线图来删除技术阻止程序。Use preview services and take dependencies on service roadmaps to remove technical blockers.