Azure 應用程式的 10 個設計原則Ten design principles for Azure applications

請遵循這些設計原則,讓您的應用程式更有擴充空間、可容易復原且更方便管理。Follow these design principles to make your application more scalable, resilient, and manageable.

自我修復設計Design for self healing. 在分散式系統中,發生失敗在所難免。In a distributed system, failures happen. 將您的應用程式設計為可在發生失敗時自我修復。Design your application to be self healing when failures occur.

讓各個項目都有備援Make all things redundant. 將備援建置到您的應用程式中,以避免發生單一失敗點。Build redundancy into your application, to avoid having single points of failure.

最小化協調Minimize coordination. 將來應用程式服務之間的協調最小化,以達成延展性。Minimize coordination between application services to achieve scalability.

相應放大的設計。設計您的應用程式,讓它可水平調整,以依需求新增或移除新的執行個體。Design to scale out. Design your application so that it can scale horizontally, adding or removing new instances as demand requires.

在限制中使用分割Partition around limits. 使用分割作業來解決資料庫、網路和計算限制。Use partitioning to work around database, network, and compute limits.

作業的設計Design for operations. 設計應用程式,讓作業小組擁有所需的工具。Design your application so that the operations team has the tools they need.

使用受管理的服務Use managed services. 可能的話,請使用平台即服務 (PaaS) 而非基礎結構即服務 (IaaS)。When possible, use platform as a service (PaaS) rather than infrastructure as a service (IaaS).

使用作業的最佳資料存放區Use the best data store for the job. 挑選最適合您資料的儲存體技術,以及了解使用方式。Pick the storage technology that is the best fit for your data and how it will be used.

進化的設計Design for evolution. 所有成功的應用程式,在經過一段時間後都會有所變更。All successful applications change over time. 進化的設計是連續創新的關鍵。An evolutionary design is key for continuous innovation.

針對企業的需求而建置Build for the needs of business. 每個設計決策必須對應某個業務需求。Every design decision must be justified by a business requirement.