- Cloud Native Development Patterns and Best Practices
- John Gilbert
- 178字
- 2021-06-30 18:43:05
Providers
For completeness, it is worthwhile to point out that there is a natural bulkhead between cloud providers. All cloud providers will have outages, but the likelihood that they will have simultaneous outages is low. In the context of polyglot cloud, where each component selects the most appropriate provider based on its needs, this simply means that when one provider has an outage then the components running on the other providers will not be affected. Maybe there is an argument to be made that your components should be well diversified across providers, but that is not the objective of polyglot cloud. On the other end of the spectrum, multi-cloud suggests running components redundantly across multiple providers to achieve high availability during an outage. I will wager that maybe 1% of companies have maybe 1% of their workloads which might benefit from all the extra elbow grease that is needed to achieve this type of topology. For the overwhelming majority of us, multi-regional deployments are quite sufficient. Regardless, in cloud-native systems these decisions are made on a component-by-component basis.
- 大數據項目管理:從規劃到實現
- AutoCAD快速入門與工程制圖
- 機器學習及應用(在線實驗+在線自測)
- Mastering VMware vSphere 6.5
- 并行數據挖掘及性能優化:關聯規則與數據相關性分析
- 輕松學Java
- Windows 8應用開發實戰
- SharePoint 2010開發最佳實踐
- 系統安裝與重裝
- 電腦主板現場維修實錄
- JavaScript典型應用與最佳實踐
- Apache Spark Quick Start Guide
- Microsoft System Center Data Protection Manager Cookbook
- Generative Adversarial Networks Projects
- ARM體系結構與編程