Azure B2C-REST API调用的延迟 [英] Azure B2C - Latency to REST API Calls

问题描述

我们正在构建一个全球分布式的应用程序，该应用程序将利用Azure B2C和REST API来丰富令牌.该应用程序可以部署在多个Azure区域中.我正在尝试找到最佳方法来最大程度地减少Azure之间的延迟 B2C和REST API.

我遇到的挑战是我不知道在哪个Azure B2C区域中运行，因此我不知道在哪个Azure区域中放置REST API.

让我们假设我在美国建立了一个Azure B2C租户，因为那是大多数用户所在的地方.用户可以使用来自美国(未知地区)或来自欧洲(未知地区)的Azure B2C.

用例1:美国用户访问Azure B2C. B2C调用REST API.当应用程序在东部时，Azure B2C有可能在西海岸运行.

-我们是否应该将REST API放在多个Azure区域中，并将Azure Traffic Manager与性能配置文件一起使用?我们将不得不将其他索赔/范围数据复制到西部，中部和东部的数据中心.

-Azure B2C是否会出于性能和灾难恢复原因而考虑ATM进行DNS更改以路由到其他API的情况?

用例2:欧洲用户访问Azure B2C.自租户在美国建立以来，是否对在美国运行的Azure B2C实例发出此请求?

-如果是这种情况，那么将我们的数据复制到欧洲将没有任何价值，因为所有请求都将始终被路由回美国.

很长的问题很抱歉.我找不到用于全局Azure B2C实施的参考材料.

解决方案

您不必担心将您的位置放在何处首先是REST API.

Azure中的任何租户，无论是B2B租户还是B2C租户-都不特定于数据中心.另外，根据您在创建承租人时选择的国家(地区)，它甚至可能不是地理中心的.

您可以通过转到 Azure Active Directory 刀片服务器来检查位置和国家/地区，然后选择 属性.

以下是Azure B2C租户测试示例的屏幕截图

测试1 :我选择了该国家作为美国.租户的位置在所有美国数据中心上.

.

测试2 :当该国家/地区被选为法国时，该位置将是所有符合欧盟标准的数据中心.

.

测试3 :但是，当我选择印度作为国家/地区时，位置是-亚洲，美国和欧洲数据中心.

.

因此，您的用户所处的位置-租户在该区域中调用REST API时，延迟应与租户位于所有该区域中的数据中心相同.

注意:这不适用于Azure德国云.在德国地区创建的所有资源/租户都只会在Azure德国，而不会在任何其他数据中心中.

 

We are building a globally distributed application that will utilize Azure B2C a REST API to enrich the token.  The application can be deployed in multiple Azure regions.  I am trying to find the best approach to minimize latency between Azure B2C and the REST API.

The challenge that I am running into is that I don't know in which Azure B2C Region is running so I don't know in which Azure region to place the REST API's.

Let's assume that I establish an Azure B2C tenant in the US because that's where the majority of the users are located.  Users can use Azure B2C from the US (unknown region) or from Europe (unknown region).

Use Case #1: US based user accesses Azure B2C.  B2C calls the REST API.  There's a potential for Azure B2C to be running on the West Coast while the application is in East.

- Should we place the REST API in multiple Azure Regions and use Azure Traffic Manager with a performance profile?  We would have to replicate our additional claim/scope data to West, Central and East data centers.

- Will Azure B2C respect the DNS changes that ATM will make to route to a different API for performance and for DR reasons as well?

Use Case #2: European based user accesses Azure B2C.  Is this request made to an Azure B2C instance running in the US since the tenant was established in the US?

- If this is the case then there would be no value to replicating our data to Europe since all requests would always be routed back to the US

Sorry about the long set of questions.  I couldn't find reference material for globally Azure B2C implementations. 

解决方案

You would not have to worry about where to place your REST API's in the first place.

Any tenant in Azure, be that B2B Tenant or B2C Tenant - is not Data Center specific. Also, depending on which Country you choose while creating the Tenant, it maynot be even Geo-Centric.

You can check the location and country by going to the Azure Active Directory Blade, then select Properties.

Here are screenshots of Test Examples for Azure B2C Tenants

Test 1:  I selected the country as United States. The location of the Tenant is on all the United States Data Centers.

.

Test 2: When the country was selected as France, the location would be all the EU Compliant Data Centers.

.

Test 3: However, when I selected India as the country, the location is - Asia, United States and Europe Data Centers.

.

Hence, where ever your users are located - when the Tenant calls for the REST API in that region, latency should remain the same as the Tenant is located among all of that regions Data Centers.

Note: This does not apply to the Azure Germany Cloud. Any and all resources/tenants created in the German Region would be only in Azure Germany and not in any other Data Centers.

 

这篇关于Azure B2C-REST API调用的延迟的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！