云设计模式

喜欢ヅ旅行 2023-09-27 18:54 90阅读 0赞

[云设计模式 - Azure Architecture Center | Microsoft Learn][- Azure Architecture Center _ Microsoft Learn]

这些设计模式可用于在云中构建可靠且可缩放的安全应用程序。

每种模式描述了该模式解决的问题、有关应用该模式的注意事项，以及基于 Microsoft Azure 的示例。 大多数模式都包含了代码示例或代码片段，演示如何在 Azure 中实现该模式。 但是，无论是托管在 Azure 上还是其他云平台中，大多数模式都与任一分布式系统相关。

### 云中开发的难题 ###

<table> 
 <tbody> 
  <tr> 
   <td><a href="https://learn.microsoft.com/zh-cn/azure/architecture/patterns/category/data-management" title="正在上传…重新上传取消" rel="nofollow">正在上传…重新上传取消</a></td> 
   <td> <h4><a href="https://learn.microsoft.com/zh-cn/azure/architecture/patterns/category/data-management" title="数据管理" rel="nofollow">数据管理</a></h4> <p>数据管理是云应用程序的关键要素，影响大部分质量属性。 数据通常托管在不同的位置并跨多个服务器，以实现性能、可伸缩性或可用性。 这可能会带来各种挑战。 例如，必须维护数据一致性，通常需要跨不同的位置同步数据。</p> </td> 
  </tr> 
  <tr> 
   <td><a href="https://learn.microsoft.com/zh-cn/azure/architecture/patterns/category/design-implementation" title="正在上传…重新上传取消" rel="nofollow">正在上传…重新上传取消</a></td> 
   <td> <h4><a href="https://learn.microsoft.com/zh-cn/azure/architecture/patterns/category/design-implementation" title="设计和实施" rel="nofollow">设计和实施</a></h4> <p>优秀的设计包含组件设计和部署中的一致性和连贯性、简化管理和开发的可维护性，以及允许组件和子系统在其他应用程序和方案中使用的可重用性。 在设计和实施阶段做出的决策对云托管应用程序和服务的质量和总拥有成本具有显著影响。</p> </td> 
  </tr> 
  <tr> 
   <td><a href="https://learn.microsoft.com/zh-cn/azure/architecture/patterns/category/messaging" title="正在上传…重新上传取消" rel="nofollow">正在上传…重新上传取消</a></td> 
   <td> <h4><a href="https://learn.microsoft.com/zh-cn/azure/architecture/patterns/category/messaging" title="消息传送" rel="nofollow">消息传送</a></h4> <p>云应用程序的分布性要求消息基础结构在理想情况下能以松散耦合的方式连接组件和服务，从而将可伸缩性最大化。 异步消息受到广泛使用并提供了诸多好处，但也带来了许多挑战，如消息排序、有害消息管理和幂等性等。</p> </td> 
  </tr> 
 </tbody> 
</table>

### 模式目录 ###

<table> 
 <thead> 
  <tr> 
   <th>模式</th> 
   <th>总结</th> 
   <th>类别</th> 
  </tr> 
 </thead> 
 <tbody> 
  <tr> 
   <td><a href="https://learn.microsoft.com/zh-cn/azure/architecture/patterns/ambassador" title="代表" rel="nofollow">代表</a></td> 
   <td>创建代表客户服务或应用程序发送网络请求的帮助程序服务。</td> 
   <td><a href="https://learn.microsoft.com/zh-cn/azure/architecture/patterns/category/design-implementation" title="设计和实现" rel="nofollow">设计和实现</a>， 
    <hr><a href="https://learn.microsoft.com/zh-cn/azure/architecture/framework/devops/devops-patterns" title="卓越运营" rel="nofollow">卓越运营</a></td> 
  </tr> 
  <tr> 
   <td><a href="https://learn.microsoft.com/zh-cn/azure/architecture/patterns/anti-corruption-layer" title="防损层" rel="nofollow">防损层</a></td> 
   <td>在现代应用程序与旧系统之间实施外观或适配器层。</td> 
   <td><a href="https://learn.microsoft.com/zh-cn/azure/architecture/patterns/category/design-implementation" title="设计和实现" rel="nofollow">设计和实现</a>， 
    <hr><a href="https://learn.microsoft.com/zh-cn/azure/architecture/framework/devops/devops-patterns" title="卓越运营" rel="nofollow">卓越运营</a></td> 
  </tr> 
  <tr> 
   <td><a href="https://learn.microsoft.com/zh-cn/azure/architecture/patterns/async-request-reply" title="异步请求-答复" rel="nofollow">异步请求-答复</a></td> 
   <td>在后端处理需要是异步处理但前端仍需要明确响应的情况下，将后端处理与前端主机分离。</td> 
   <td><a href="https://learn.microsoft.com/zh-cn/azure/architecture/patterns/category/messaging" title="消息传送" rel="nofollow">消息传送</a></td> 
  </tr> 
  <tr> 
   <td><a href="https://learn.microsoft.com/zh-cn/azure/architecture/patterns/backends-for-frontends" title="用于前端的后端" rel="nofollow">用于前端的后端</a></td> 
   <td>创建单独的后端服务，供特定的前端应用程序或接口使用。</td> 
   <td><a href="https://learn.microsoft.com/zh-cn/azure/architecture/patterns/category/design-implementation" title="设计和实施" rel="nofollow">设计和实施</a></td> 
  </tr> 
  <tr> 
   <td><a href="https://learn.microsoft.com/zh-cn/azure/architecture/patterns/bulkhead" title="隔层" rel="nofollow">隔层</a></td> 
   <td>将应用程序的元素隔离到池中，这样，如果一个元素发生故障，其他元素可继续工作。</td> 
   <td><a href="https://learn.microsoft.com/zh-cn/azure/architecture/framework/resiliency/reliability-patterns" title="可靠性" rel="nofollow">可靠性</a></td> 
  </tr> 
  <tr> 
   <td><a href="https://learn.microsoft.com/zh-cn/azure/architecture/patterns/cache-aside" title="缓存端" rel="nofollow">缓存端</a></td> 
   <td>将数据按需从数据存储加载到缓存中</td> 
   <td><a href="https://learn.microsoft.com/zh-cn/azure/architecture/patterns/category/data-management" title="数据管理" rel="nofollow">数据管理</a>， 
    <hr><a href="https://learn.microsoft.com/zh-cn/azure/architecture/framework/scalability/performance-efficiency-patterns" title="性能效率" rel="nofollow">性能效率</a></td> 
  </tr> 
  <tr> 
   <td><a href="https://learn.microsoft.com/zh-cn/azure/architecture/patterns/choreography" title="协调" rel="nofollow">协调</a></td> 
   <td>让每项服务都参与决定业务运营的处理时间和处理方式，而不是依赖于一个中心型业务流程协调程序。</td> 
   <td><a href="https://learn.microsoft.com/zh-cn/azure/architecture/patterns/category/messaging" title="消息传送" rel="nofollow">消息传送</a>， 
    <hr><a href="https://learn.microsoft.com/zh-cn/azure/architecture/framework/scalability/performance-efficiency-patterns" title="性能效率" rel="nofollow">性能效率</a></td> 
  </tr> 
  <tr> 
   <td><a href="https://learn.microsoft.com/zh-cn/azure/architecture/patterns/circuit-breaker" title="断路器" rel="nofollow">断路器</a></td> 
   <td>连接到远程服务或资源时处理故障，此类故障所需修复时间不定。</td> 
   <td><a href="https://learn.microsoft.com/zh-cn/azure/architecture/framework/resiliency/reliability-patterns" title="可靠性" rel="nofollow">可靠性</a></td> 
  </tr> 
  <tr> 
   <td><a href="https://learn.microsoft.com/zh-cn/azure/architecture/patterns/claim-check" title="声明检查" rel="nofollow">声明检查</a></td> 
   <td>将大型消息拆分成声明检查和有效负载，以免消息总线过载。</td> 
   <td><a href="https://learn.microsoft.com/zh-cn/azure/architecture/patterns/category/messaging" title="消息传送" rel="nofollow">消息传送</a></td> 
  </tr> 
  <tr> 
   <td><a href="https://learn.microsoft.com/zh-cn/azure/architecture/patterns/compensating-transaction" title="补偿事务" rel="nofollow">补偿事务</a></td> 
   <td>撤销一系列会共同定义最终一致操作的工作。</td> 
   <td><a href="https://learn.microsoft.com/zh-cn/azure/architecture/framework/resiliency/reliability-patterns" title="可靠性" rel="nofollow">可靠性</a></td> 
  </tr> 
  <tr> 
   <td><a href="https://learn.microsoft.com/zh-cn/azure/architecture/patterns/competing-consumers" title="竞争性使用者" rel="nofollow">竞争性使用者</a></td> 
   <td>使多个并发使用者能够处理同一消息通道上收到的消息。</td> 
   <td><a href="https://learn.microsoft.com/zh-cn/azure/architecture/patterns/category/messaging" title="消息传送" rel="nofollow">消息传送</a></td> 
  </tr> 
  <tr> 
   <td><a href="https://learn.microsoft.com/zh-cn/azure/architecture/patterns/compute-resource-consolidation" title="计算资源合并" rel="nofollow">计算资源合并</a></td> 
   <td>将多个任务或操作合并到单个计算单元</td> 
   <td><a href="https://learn.microsoft.com/zh-cn/azure/architecture/patterns/category/design-implementation" title="设计和实施" rel="nofollow">设计和实施</a></td> 
  </tr> 
  <tr> 
   <td><a href="https://learn.microsoft.com/zh-cn/azure/architecture/patterns/cqrs" title="CQRS" rel="nofollow">CQRS</a></td> 
   <td>使用独立接口将读取数据的操作与更新数据的操作分离。</td> 
   <td><a href="https://learn.microsoft.com/zh-cn/azure/architecture/patterns/category/data-management" title="数据管理" rel="nofollow">数据管理</a>， 
    <hr><a href="https://learn.microsoft.com/zh-cn/azure/architecture/patterns/category/design-implementation" title="设计和实现" rel="nofollow">设计和实现</a>， 
    <hr><a href="https://learn.microsoft.com/zh-cn/azure/architecture/framework/scalability/performance-efficiency-patterns" title="性能效率" rel="nofollow">性能效率</a></td> 
  </tr> 
  <tr> 
   <td><a href="https://learn.microsoft.com/zh-cn/azure/architecture/patterns/deployment-stamp" title="部署戳" rel="nofollow">部署戳</a></td> 
   <td>部署应用程序组件的多个独立副本，包括数据存储。</td> 
   <td><a href="https://learn.microsoft.com/zh-cn/azure/architecture/framework/resiliency/reliability-patterns" title="可靠性" rel="nofollow">可靠性</a>， 
    <hr><a href="https://learn.microsoft.com/zh-cn/azure/architecture/framework/scalability/performance-efficiency-patterns" title="性能效率" rel="nofollow">性能效率</a></td> 
  </tr> 
  <tr> 
   <td><a href="https://learn.microsoft.com/zh-cn/azure/architecture/patterns/edge-workload-configuration" title="边缘工作负载配置" rel="nofollow">边缘工作负载配置</a></td> 
   <td>由于车间系统和设备种类繁多，使得配置工作负载困难重重。</td> 
   <td><a href="https://learn.microsoft.com/zh-cn/azure/architecture/patterns/category/design-implementation" title="设计和实施" rel="nofollow">设计和实施</a></td> 
  </tr> 
  <tr> 
   <td><a href="https://learn.microsoft.com/zh-cn/azure/architecture/patterns/event-sourcing" title="事件溯源" rel="nofollow">事件溯源</a></td> 
   <td>使用只追加存储来记录描述域中数据采取的操作的完整系列事件。</td> 
   <td><a href="https://learn.microsoft.com/zh-cn/azure/architecture/patterns/category/data-management" title="数据管理" rel="nofollow">数据管理</a>， 
    <hr><a href="https://learn.microsoft.com/zh-cn/azure/architecture/framework/scalability/performance-efficiency-patterns" title="性能效率" rel="nofollow">性能效率</a></td> 
  </tr> 
  <tr> 
   <td><a href="https://learn.microsoft.com/zh-cn/azure/architecture/patterns/external-configuration-store" title="外部配置存储" rel="nofollow">外部配置存储</a></td> 
   <td>将配置信息从应用程序部署包移出，移到一个集中的位置。</td> 
   <td><a href="https://learn.microsoft.com/zh-cn/azure/architecture/patterns/category/design-implementation" title="设计和实现" rel="nofollow">设计和实现</a>， 
    <hr><a href="https://learn.microsoft.com/zh-cn/azure/architecture/framework/devops/devops-patterns" title="卓越运营" rel="nofollow">卓越运营</a></td> 
  </tr> 
  <tr> 
   <td><a href="https://learn.microsoft.com/zh-cn/azure/architecture/patterns/federated-identity" title="联合标识" rel="nofollow">联合标识</a></td> 
   <td>将身份验证委托给外部标识提供者。</td> 
   <td><a href="https://learn.microsoft.com/zh-cn/azure/architecture/framework/security/security-patterns" title="安全性" rel="nofollow">安全性</a></td> 
  </tr> 
  <tr> 
   <td><a href="https://learn.microsoft.com/zh-cn/azure/architecture/patterns/gatekeeper" title="守护程序" rel="nofollow">守护程序</a></td> 
   <td>通过使用专用的主机实例保护应用程序和服务，该实例用于充当客户端和应用程序或服务之间的中转站、验证和整理请求，并在它们之间传递请求和数据。</td> 
   <td><a href="https://learn.microsoft.com/zh-cn/azure/architecture/framework/security/security-patterns" title="安全性" rel="nofollow">安全性</a></td> 
  </tr> 
  <tr> 
   <td><a href="https://learn.microsoft.com/zh-cn/azure/architecture/patterns/gateway-aggregation" title="网关聚合" rel="nofollow">网关聚合</a></td> 
   <td>使用网关可将多个单独请求聚合成一个请求。</td> 
   <td><a href="https://learn.microsoft.com/zh-cn/azure/architecture/patterns/category/design-implementation" title="设计和实现" rel="nofollow">设计和实现</a>， 
    <hr><a href="https://learn.microsoft.com/zh-cn/azure/architecture/framework/devops/devops-patterns" title="卓越运营" rel="nofollow">卓越运营</a></td> 
  </tr> 
  <tr> 
   <td><a href="https://learn.microsoft.com/zh-cn/azure/architecture/patterns/gateway-offloading" title="网关卸载" rel="nofollow">网关卸载</a></td> 
   <td>将共享或专用服务功能卸载到网关代理。</td> 
   <td><a href="https://learn.microsoft.com/zh-cn/azure/architecture/patterns/category/design-implementation" title="设计和实现" rel="nofollow">设计和实现</a>， 
    <hr><a href="https://learn.microsoft.com/zh-cn/azure/architecture/framework/devops/devops-patterns" title="卓越运营" rel="nofollow">卓越运营</a></td> 
  </tr> 
  <tr> 
   <td><a href="https://learn.microsoft.com/zh-cn/azure/architecture/patterns/gateway-routing" title="网关路由" rel="nofollow">网关路由</a></td> 
   <td>使用单个终结点将请求路由到多个服务。</td> 
   <td><a href="https://learn.microsoft.com/zh-cn/azure/architecture/patterns/category/design-implementation" title="设计和实现" rel="nofollow">设计和实现</a>， 
    <hr><a href="https://learn.microsoft.com/zh-cn/azure/architecture/framework/devops/devops-patterns" title="卓越运营" rel="nofollow">卓越运营</a></td> 
  </tr> 
  <tr> 
   <td><a href="https://learn.microsoft.com/zh-cn/azure/architecture/patterns/geodes" title="Geodes" rel="nofollow">Geodes</a></td> 
   <td>将后端服务部署到一组地理节点，其中的每个节点可为任何区域中的任何客户端请求提供服务。</td> 
   <td><a href="https://learn.microsoft.com/zh-cn/azure/architecture/framework/resiliency/reliability-patterns" title="可靠性" rel="nofollow">可靠性</a>， 
    <hr><a href="https://learn.microsoft.com/zh-cn/azure/architecture/framework/devops/devops-patterns" title="卓越运营" rel="nofollow">卓越运营</a></td> 
  </tr> 
  <tr> 
   <td><a href="https://learn.microsoft.com/zh-cn/azure/architecture/patterns/health-endpoint-monitoring" title="运行状况终结点监视" rel="nofollow">运行状况终结点监视</a></td> 
   <td>在应用程序中实施可让外部工具通过公开终结点定期访问的功能检查。</td> 
   <td><a href="https://learn.microsoft.com/zh-cn/azure/architecture/framework/resiliency/reliability-patterns" title="可靠性" rel="nofollow">可靠性</a>， 
    <hr><a href="https://learn.microsoft.com/zh-cn/azure/architecture/framework/devops/devops-patterns" title="卓越运营" rel="nofollow">卓越运营</a></td> 
  </tr> 
  <tr> 
   <td><a href="https://learn.microsoft.com/zh-cn/azure/architecture/patterns/index-table" title="索引表" rel="nofollow">索引表</a></td> 
   <td>基于数据存储中经常由查询引用的字段创建索引。</td> 
   <td><a href="https://learn.microsoft.com/zh-cn/azure/architecture/patterns/category/data-management" title="数据管理" rel="nofollow">数据管理</a>， 
    <hr><a href="https://learn.microsoft.com/zh-cn/azure/architecture/framework/scalability/performance-efficiency-patterns" title="性能效率" rel="nofollow">性能效率</a></td> 
  </tr> 
  <tr> 
   <td><a href="https://learn.microsoft.com/zh-cn/azure/architecture/patterns/leader-election" title="领导选择" rel="nofollow">领导选择</a></td> 
   <td>通过选拔一个实例作为领导来负责管理其他实例，协调分布式应用程序中协作性任务实例集合所执行的操作。</td> 
   <td><a href="https://learn.microsoft.com/zh-cn/azure/architecture/patterns/category/design-implementation" title="设计和实现" rel="nofollow">设计和实现</a>， 
    <hr><a href="https://learn.microsoft.com/zh-cn/azure/architecture/framework/resiliency/reliability-patterns" title="可靠性" rel="nofollow">可靠性</a></td> 
  </tr> 
  <tr> 
   <td><a href="https://learn.microsoft.com/zh-cn/azure/architecture/patterns/materialized-view" title="具体化视图" rel="nofollow">具体化视图</a></td> 
   <td>当未针对所需的查询操作完美设置数据的格式时，在一个或多个数据存储中基于数据生成预填充的视图。</td> 
   <td><a href="https://learn.microsoft.com/zh-cn/azure/architecture/patterns/category/data-management" title="数据管理" rel="nofollow">数据管理</a>， 
    <hr><a href="https://learn.microsoft.com/zh-cn/azure/architecture/framework/devops/devops-patterns" title="卓越运营" rel="nofollow">卓越运营</a></td> 
  </tr> 
  <tr> 
   <td><a href="https://learn.microsoft.com/zh-cn/azure/architecture/patterns/pipes-and-filters" title="管道和筛选器" rel="nofollow">管道和筛选器</a></td> 
   <td>将一个执行复杂处理的任务分解为一系列可重复使用的单个元素。</td> 
   <td><a href="https://learn.microsoft.com/zh-cn/azure/architecture/patterns/category/design-implementation" title="设计和实现" rel="nofollow">设计和实现</a>， 
    <hr><a href="https://learn.microsoft.com/zh-cn/azure/architecture/patterns/category/messaging" title="消息传送" rel="nofollow">消息传送</a></td> 
  </tr> 
  <tr> 
   <td><a href="https://learn.microsoft.com/zh-cn/azure/architecture/patterns/priority-queue" title="优先级队列" rel="nofollow">优先级队列</a></td> 
   <td>为发送到服务的请求确定优先级，以便高优先级请求能够得到比低优先级请求更快速地接收和处理。</td> 
   <td><a href="https://learn.microsoft.com/zh-cn/azure/architecture/patterns/category/messaging" title="消息传送" rel="nofollow">消息传送</a>， 
    <hr><a href="https://learn.microsoft.com/zh-cn/azure/architecture/framework/scalability/performance-efficiency-patterns" title="性能效率" rel="nofollow">性能效率</a></td> 
  </tr> 
  <tr> 
   <td><a href="https://learn.microsoft.com/zh-cn/azure/architecture/patterns/publisher-subscriber" title="发布方/订阅方" rel="nofollow">发布方/订阅方</a></td> 
   <td>使应用程序能够以异步方式向多个感兴趣的使用者公布事件，而无需将发送方与接收方耦合。</td> 
   <td><a href="https://learn.microsoft.com/zh-cn/azure/architecture/patterns/category/messaging" title="消息传送" rel="nofollow">消息传送</a></td> 
  </tr> 
  <tr> 
   <td><a href="https://learn.microsoft.com/zh-cn/azure/architecture/patterns/queue-based-load-leveling" title="基于队列的负载调控" rel="nofollow">基于队列的负载调控</a></td> 
   <td>使用队列在任务与所调用的服务之间充当缓冲，从而缓解间歇性负载过大现象。</td> 
   <td><a href="https://learn.microsoft.com/zh-cn/azure/architecture/framework/resiliency/reliability-patterns" title="可靠性" rel="nofollow">可靠性</a>， 
    <hr><a href="https://learn.microsoft.com/zh-cn/azure/architecture/patterns/category/messaging" title="消息传送" rel="nofollow">消息传送</a>， 
    <hr><a href="https://learn.microsoft.com/zh-cn/azure/architecture/framework/resiliency/reliability-patterns" title="复原能力" rel="nofollow">复原能力</a>， 
    <hr><a href="https://learn.microsoft.com/zh-cn/azure/architecture/framework/scalability/performance-efficiency-patterns" title="性能效率" rel="nofollow">性能效率</a></td> 
  </tr> 
  <tr> 
   <td><a href="https://learn.microsoft.com/zh-cn/azure/architecture/patterns/rate-limiting-pattern" title="速率限制模式" rel="nofollow">速率限制模式</a></td> 
   <td>速率限制模式可帮助避免或尽量减少与这些限制相关的限制错误，并帮助更准确地预测吞吐量。</td> 
   <td><a href="https://learn.microsoft.com/zh-cn/azure/architecture/framework/resiliency/reliability-patterns" title="可靠性" rel="nofollow">可靠性</a></td> 
  </tr> 
  <tr> 
   <td><a href="https://learn.microsoft.com/zh-cn/azure/architecture/patterns/retry" title="重试" rel="nofollow">重试</a></td> 
   <td>当应用程序尝试连接到服务或网络资源时，使应用程序能够通过以透明方式重试先前失败的操作来处理预期的临时故障。</td> 
   <td><a href="https://learn.microsoft.com/zh-cn/azure/architecture/framework/resiliency/reliability-patterns" title="可靠性" rel="nofollow">可靠性</a></td> 
  </tr> 
  <tr> 
   <td><a href="https://learn.microsoft.com/zh-cn/azure/architecture/reference-architectures/saga/saga" title="一系列事件" rel="nofollow">一系列事件</a></td> 
   <td>在分布式事务方案中跨微服务管理数据一致性。 Saga 是一系列事务，用于更新每项服务并发布消息或事件来触发下一个事务步骤。</td> 
   <td><a href="https://learn.microsoft.com/zh-cn/azure/architecture/patterns/category/messaging" title="消息传送" rel="nofollow">消息传送</a></td> 
  </tr> 
  <tr> 
   <td><a href="https://learn.microsoft.com/zh-cn/azure/architecture/patterns/scheduler-agent-supervisor" title="计划程序代理监督程序" rel="nofollow">计划程序代理监督程序</a></td> 
   <td>跨一组分布式服务和其他远程资源协调一组操作。</td> 
   <td><a href="https://learn.microsoft.com/zh-cn/azure/architecture/patterns/category/messaging" title="消息传送" rel="nofollow">消息传送</a>， 
    <hr><a href="https://learn.microsoft.com/zh-cn/azure/architecture/framework/resiliency/reliability-patterns" title="可靠性" rel="nofollow">可靠性</a></td> 
  </tr> 
  <tr> 
   <td><a href="https://learn.microsoft.com/zh-cn/azure/architecture/patterns/sequential-convoy" title="顺序保护" rel="nofollow">顺序保护</a></td> 
   <td>按定义的顺序处理一组相关的消息，不需阻止对其他消息组的处理。</td> 
   <td><a href="https://learn.microsoft.com/zh-cn/azure/architecture/patterns/category/messaging" title="消息传送" rel="nofollow">消息传送</a></td> 
  </tr> 
  <tr> 
   <td><a href="https://learn.microsoft.com/zh-cn/azure/architecture/patterns/sharding" title="分片" rel="nofollow">分片</a></td> 
   <td>将数据存储划分为一组水平分区或分片。</td> 
   <td><a href="https://learn.microsoft.com/zh-cn/azure/architecture/patterns/category/data-management" title="数据管理" rel="nofollow">数据管理</a>， 
    <hr><a href="https://learn.microsoft.com/zh-cn/azure/architecture/framework/scalability/performance-efficiency-patterns" title="性能效率" rel="nofollow">性能效率</a></td> 
  </tr> 
  <tr> 
   <td><a href="https://learn.microsoft.com/zh-cn/azure/architecture/patterns/sidecar" title="Sidecar" rel="nofollow">Sidecar</a></td> 
   <td>将应用程序的组件部署到单独的进程或容器中，以提供隔离和封装。</td> 
   <td><a href="https://learn.microsoft.com/zh-cn/azure/architecture/patterns/category/design-implementation" title="设计和实现" rel="nofollow">设计和实现</a>， 
    <hr><a href="https://learn.microsoft.com/zh-cn/azure/architecture/framework/devops/devops-patterns" title="卓越运营" rel="nofollow">卓越运营</a></td> 
  </tr> 
  <tr> 
   <td><a href="https://learn.microsoft.com/zh-cn/azure/architecture/patterns/static-content-hosting" title="静态内容托管" rel="nofollow">静态内容托管</a></td> 
   <td>将静态内容部署到基于云的存储服务，再由后者将它们直接传送给客户端。</td> 
   <td><a href="https://learn.microsoft.com/zh-cn/azure/architecture/patterns/category/design-implementation" title="设计和实现" rel="nofollow">设计和实现</a>， 
    <hr><a href="https://learn.microsoft.com/zh-cn/azure/architecture/patterns/category/data-management" title="数据管理" rel="nofollow">数据管理</a>， 
    <hr><a href="https://learn.microsoft.com/zh-cn/azure/architecture/framework/scalability/performance-efficiency-patterns" title="性能效率" rel="nofollow">性能效率</a></td> 
  </tr> 
  <tr> 
   <td><a href="https://learn.microsoft.com/zh-cn/azure/architecture/patterns/strangler-fig" title="Strangler Fig" rel="nofollow">Strangler Fig</a></td> 
   <td>通过将特定的功能片断逐渐取代为新的应用程序和服务，逐步迁移旧系统。</td> 
   <td><a href="https://learn.microsoft.com/zh-cn/azure/architecture/patterns/category/design-implementation" title="设计和实现" rel="nofollow">设计和实现</a>， 
    <hr><a href="https://learn.microsoft.com/zh-cn/azure/architecture/framework/devops/devops-patterns" title="卓越运营" rel="nofollow">卓越运营</a></td> 
  </tr> 
  <tr> 
   <td><a href="https://learn.microsoft.com/zh-cn/azure/architecture/patterns/throttling" title="限制" rel="nofollow">限制</a></td> 
   <td>控制应用程序实例、单个租户或整个服务对资源的消耗。</td> 
   <td><a href="https://learn.microsoft.com/zh-cn/azure/architecture/framework/resiliency/reliability-patterns" title="可靠性" rel="nofollow">可靠性</a>， 
    <hr><a href="https://learn.microsoft.com/zh-cn/azure/architecture/framework/scalability/performance-efficiency-patterns" title="性能效率" rel="nofollow">性能效率</a></td> 
  </tr> 
  <tr> 
   <td><a href="https://learn.microsoft.com/zh-cn/azure/architecture/patterns/valet-key" title="附属密钥" rel="nofollow">附属密钥</a></td> 
   <td>使用令牌或密钥，向客户端授予对特定资源或服务的受限直接访问权限。</td> 
   <td><a href="https://learn.microsoft.com/zh-cn/azure/architecture/patterns/category/data-management" title="数据管理" rel="nofollow">数据管理</a>， 
    <hr><a href="https://learn.microsoft.com/zh-cn/azure/architecture/framework/security/security-patterns" title="安全性" rel="nofollow">安全性</a></td> 
  </tr> 
 </tbody> 
</table>

--------------------

### 建议的内容 ###

*  #### [设计和实现模式 - Cloud Design Patterns][- Cloud Design Patterns] ####
    
    使用这些设计和实现模式可以简化云应用程序的管理、开发和可重用性。
 *  #### [自我修复型设计 - Azure Application Architecture Guide][- Azure Application Architecture Guide] ####
    
    了解如何设计可从故障中恢复的可复原应用程序，而无需通过自我修复进行人工干预。
 *  #### [数据管理模式 - Cloud Design Patterns][- Cloud Design Patterns 1] ####
    
    为云应用程序使用这些数据管理模式。 数据管理是一个关键元素，它会影响大部分质量属性。
 *  #### [代表模式 - Azure Architecture Center][- Azure Architecture Center] ####
    
    了解代表模式，该模式创建代表使用者服务或应用程序发送网络请求的帮助程序服务。
 *  #### [计算资源合并模式 - Azure Architecture Center][- Azure Architecture Center 1] ####
    
    使用计算资源合并设计模式将多个任务或操作合并到单个计算单元中。
 *  #### [网关路由模式 - Azure Architecture Center][- Azure Architecture Center 2] ####
    
    使用网关路由设计模式通过单个终结点将请求路由到多个服务。
 *  #### [地理节点模式 - Azure Architecture Center][- Azure Architecture Center 3] ####
    
    将后端服务部署到一组地理节点，其中的每个节点可为任何区域中的任何客户端请求提供服务。
 *  #### [微服务体系结构样式 - Azure Architecture Center][- Azure Architecture Center 4] ####
    
    了解 Azure 上的微服务体系结构样式的优点、挑战和最佳做法。

显示较少选项

[- Azure Architecture Center _ Microsoft Learn]: https://learn.microsoft.com/zh-cn/azure/architecture/patterns/
[- Cloud Design Patterns]: https://learn.microsoft.com/zh-cn/azure/architecture/patterns/category/design-implementation?source=recommendations
[- Azure Application Architecture Guide]: https://learn.microsoft.com/zh-cn/azure/architecture/guide/design-principles/self-healing?source=recommendations
[- Cloud Design Patterns 1]: https://learn.microsoft.com/zh-cn/azure/architecture/patterns/category/data-management?source=recommendations
[- Azure Architecture Center]: https://learn.microsoft.com/zh-cn/azure/architecture/patterns/ambassador?source=recommendations
[- Azure Architecture Center 1]: https://learn.microsoft.com/zh-cn/azure/architecture/patterns/compute-resource-consolidation?source=recommendations
[- Azure Architecture Center 2]: https://learn.microsoft.com/zh-cn/azure/architecture/patterns/gateway-routing?source=recommendations
[- Azure Architecture Center 3]: https://learn.microsoft.com/zh-cn/azure/architecture/patterns/geodes?source=recommendations
[- Azure Architecture Center 4]: https://learn.microsoft.com/zh-cn/azure/architecture/guide/architecture-styles/microservices?source=recommendations