全球部署:多租户或租户内位置是最佳选择吗? [英] Global Deployments: Is Multi-tenant or Intra-tenant locations the best way to go?

查看:69
本文介绍了全球部署:多租户或租户内位置是最佳选择吗?的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

  • 创建一个位于美国的位置的资源组
  • 架构B(双租户):

      在美国区域创建基于美国的RG的Azure租户
    1. 上面的双租户结构是否会与单租户形成某种可衡量的差异(假设所有vNetwork,VM等都是相同的)?我认为单租户设置会更快,因为(大概)流量永远不会离开 Azure Service Fabric.但这只是猜测.显然,资源在一起越近,连接速度就越快.但是,跨不同数据中心资源的连接仍然非常快.

      作为旁注,您无需在不同区域中创建资源组即可将资源放置在其他位置.资源组只是资源的逻辑构造.因此,您可以在美国东部部署资源组,并在欧盟托管所有服务.

      如果将所有资源都保留在同一Vnet和同一数据中心中,则将获得更高的性能.但是同样,速度的增加是最小的.在从美国到欧盟的通信服务中,您应该不会有任何问题.

      因此,总的来说,我建议使用选项A来简化配置.


      I have been tasked with building a PoC in Azure to "simulate" a future global deployment where data transfer time is important factor. The actual deployment will be using fully on-prem resources. So, as odd as it sounds, I am looking for the worse performance possible between the two options.

      Architecture A (single tenant):

      1. Create a single Azure tenant in the US region
      2. Create a Resource Group with a US-based location
      3. Create another Resource Group with an EU-based location

      Architecture B (dual tenant):

      1. Create an Azure tenant in the US region with a US-based RG
      2. Create an entirely separate Azure tenant in an EU region with a EU-based RG

      Would the dual-tenant structure above make any measurable difference one way or the other from the single-tenant (assuming all vNetwork, VMs, etc are identical)? I am thinking the single-tenant setup would be faster since (presumably) the traffic never leaves the Azure Service Fabric. But that's just speculation.

      解决方案

      Either way you shouldn't notice much of a performance difference. Obviously the closer the resources are together the faster the connection. But connection across resources in different data centers is still incredibly fast. 

      As a side note, you do not need to create resource groups in different regions to put resources in other locations. A resource group is just a logical construct of resources. So you can deploy a resource group in East US and host all your services in EU. It will not make a difference. 

      You will see increased performance if you can keep all the resources on the same Vnet and in the same data center. But again, the speed increase is minimal. You shouldnt have any issues with communicating services across from US to EU. 

      So overall, I would suggest using option A to simply the configuration. 


      这篇关于全球部署:多租户或租户内位置是最佳选择吗?的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

  • 查看全文
    登录 关闭
    扫码关注1秒登录
    发送“验证码”获取 | 15天全站免登陆