選取您的 Cookie 偏好設定

我們使用提供自身網站和服務所需的基本 Cookie 和類似工具。我們使用效能 Cookie 收集匿名統計資料,以便了解客戶如何使用我們的網站並進行改進。基本 Cookie 無法停用,但可以按一下「自訂」或「拒絕」以拒絕效能 Cookie。

如果您同意,AWS 與經核准的第三方也會使用 Cookie 提供實用的網站功能、記住您的偏好設定,並顯示相關內容,包括相關廣告。若要接受或拒絕所有非必要 Cookie,請按一下「接受」或「拒絕」。若要進行更詳細的選擇,請按一下「自訂」。

Software and architecture patterns - SaaS Lens
此頁面尚未翻譯為您的語言。 請求翻譯

Software and architecture patterns

SaaS SUS 1: How do you use deployment models (silo, bridge, pool) to align tenant consumption with resource utilization?
  • Best Practice–01: Have a good understanding of the key value and principles behind the silo, pool, and bridge models, including awareness how silo and pool strategies can be applied more granularly across the layers and services of your solution.

  • Best Practice–02: Understand the operational tradeoffs of each model. Build a unified onboarding, operations, and analytics experience spanning any of these models. 

  • Best Practice–03: Have a complete end-to-end automated tenant onboarding process that maps the tenancy models to the resources that are provisioned at each architecture layer or component. Also have detailed insights into the footprint and consumption costs and tradeoffs associated with each of these models

SaaS applications can be built using a variety of different architectural models. Regulatory, competitive, strategic, cost efficiency, and market considerations all influence the shape of your SaaS architecture. At the same time, there are strategies and patterns that can be applied when defining the footprint of the components within a SaaS application. These patterns—silo, bridge, and pool—can be applied in combinations to enable the most efficient consumption of infrastructure resources.

AWS services recommendation:

隱私權網站條款Cookie 偏好設定
© 2025, Amazon Web Services, Inc.或其附屬公司。保留所有權利。