Geo-replication and Auto-failover Groups in Azure SQL | Azure SQL for beginners (Ep. 51)

preview_player
Показать описание


0:00 Introduction
0:15 Active geo-replication vs auto-failover groups comparison
2:05 Geo-replication architecture
3:00 Auto-failover groups architecture


🔔 Subscribe to our channels for even more tips:

✔️ Additional Resources:

#AzureSQL #AzureSQLforbeginners #LearnAzureSQL #DataExposed #Azure #SQL
Рекомендации по теме
Комментарии
Автор

If we create a vnet peering from one tenant to the another tenant. Can we use the azure sql db replication cross tenant?

spykids
Автор

Hi Team :) !
Nice explains :)
So which solution should I use if I want to have 2-3 available regions (US/Europe/Asia) in configuration active/active if I want to keep the min lover latency ?

Of course I have three already made App Service in these three regions and if my customer is from US then should login by US app, from Europe to Europe endpoint etc..

But if US or Europe down, clients should be redirect to the first closer region.

Which option in Azure SQL Server should I use ? Geo-replication or Auto-Failover ?

Kuba_MotoPodlasie
Автор

For me as a naive I am trying to understand why should I considering Geo-replication or even auto-failover if Azure gives me such amazing features in business critical service tier and even in hyperscale where I can just switch a button and have a read-replica for me in another region (at least in Azure SQL Database option) and have all facilities that service fabric provides me. Could you describe a little about that?

renatobertolaccini
visit shbcf.ru