简体   繁体   English

我是否需要带有Azure API服务的Azure Traffic Manager?

[英]Do I need Azure Traffic Manager with Azure API Services?

My goal is to host web APIs in Azure using API Services using Azure Service Fabric. 我的目标是通过使用Azure Service Fabric的API Services在Azure中托管Web API。 Azure Traffic Manager seemed to gear towards Infrastructure As A Service (IAAS) for its service such load balancing, fault tolerance etc. The Azure Service Fabric is geared towards Platform As A Service (PAAS) model with its own clustering. Azure Traffic Manager似乎针对其服务(例如负载平衡,容错等)而面向基础架构即服务(IAAS)。AzureService Fabric面向具有自身群集的平台即服务(PAAS)模型。 If my goal is to host web APIs (authored by leveraging Azure Service Fabric and without the need for Web Apps) in Azure, can I skip using Azure Traffic Manager because Service Fabric already provides the clustering? 如果我的目标是在Azure中托管Web API(通过利用Azure Service Fabric编写而无需使用Web Apps),由于Service Fabric已经提供了群集,是否可以跳过使用Azure Traffic Manager? If not, then why should I use the Azure Traffic Manager? 如果没有,那为什么我应该使用Azure Traffic Manager? Am I missing something? 我想念什么吗?

You are missing the fact that everything you have mentioned in there is reliant on a single region and that occasionally regions die. 您错过了以下事实:您在其中提到的所有内容都依赖于单个区域,并且有时区域会消失。

If you have a Service Fabric located in West Europe for instance, and the West Europe region dies you have lost your entire solution. 例如,如果您的服务结构位于西欧,而西欧地区死亡,则您将失去整个解决方案。

If you have a Service Fabric in West Europe and North Europe, with data replicated, and a Traffic Manager profile spread across the two of them. 如果您在西欧和北欧拥有Service Fabric,并且复制了数据,并且Traffic Manager概要文件分布在这两个之间。 In that instance when a region dies, you still have a working solution. 在那种情况下,当一个区域死亡时,您仍然有一个可行的解决方案。

When building an available solution, you need to be able to point to any item within a solution and ask what happens if it fails. 构建可用的解决方案时,您需要能够指向解决方案中的任何项目,并询问如果失败会发生什么情况。 That should go from a VM to a whole region of datacenters. 那应该从VM到整个数据中心区域。

Of course you need to weigh that against the cost of replicating your entire solution to another DC purely for reliance purposes. 当然,您需要权衡该成本与纯粹出于可靠性目的将整个解决方案复制到另一个DC的成本。 Region failures are very rare occurrences and you if you can handle some downtime you might be better simply ensuring your data is replicated to another region (by using GRS storage) and having a process to bring that data back online from another region. 区域故障很少发生,如果您可以处理一些停机时间,则最好只是确保将数据复制到另一个区域(通过使用GRS存储),然后制定一个流程使该数据从另一个区域恢复联机。

But of course by doing that, you have made a decision about what you want to happen in the event of that failure. 但是,当然,通过这样做,您可以确定发生故障时要发生的情况。 Which is the whole point. 这才是重点。

声明:本站的技术帖子网页,遵循CC BY-SA 4.0协议,如果您需要转载,请注明本站网址或者原文地址。任何问题请咨询:yoyou2525@163.com.

 
粤ICP备18138465号  © 2020-2024 STACKOOM.COM