Azure comes up with 2 very important features of Geo-Replication and Failover mechanism which are very relevant in today's world of a distributed application. In this blog, we will try to cover the basics of these topics
SQL DB - Azure Geo-Replication - Most of the time data is very critical to the client and he doesn't want to lose any data in terms of hardware failure.
- With Azure geo-replication, the client has the flexibility to choose any other region which he will use if there is any failure.
- While creating a database for the application, the client can opt for the Geo-replication option which will create SQL DB in different regions which the client opts for.
- If one region goes down, DB in another region is available and in the application, we need to change the connection string for another server.
- Changing DB connection string required manual intervention in the application of configuration
SQL DB - Auto Failover - SQL DB Auto failover lets another DB comes into the picture automatically if one DB goes down.
- It is a wrapper over Azure Geo-Replication.
- Here one region act as primary and the other act as secondary.
- If primary goes down, secondary will come into the picture and the user doesn't need to change any connection string in the application
- No manual intervention is required as it's an automatic failover technique and needs to configure only once, after that azure will take care of all changes.
Hope this will give you some insight.
Happy Coding
Cheers !!!!
Join the conversation! Your thoughts help the community grow.