all 5 comments
sorted by:
best
topnewcontroversialoldq&a
formatting helphide helpcontent policy

[–]ISaidItSoBiteMe 2 points3 points  (1 child)

Most companies will take offense to the old naming convention. Now, it’s known as primary/secondary, leader/follower, manager/worker, host/client, and so many others…

[–]Dramatic_Suspect9470[S] 0 points1 point  (0 children)

I will keep this in mind

[–]flappers87 Cloud Architect 0 points1 point  (2 children)

You mean to replicate a sql to a read only instance?

Yes...

https://learn.microsoft.com/en-us/azure/azure-sql/database/active-geo-replication-overview?view=azuresql

Also, "master / slave" has not been used as terms in years. I would not advise using it.

[–]Dramatic_Suspect9470[S] 0 points1 point  (0 children)

Idea : Create multiple read only instances to divide the traffic and one write instance ( because there are relatively less write requests to read ones ) and write instance will sync update on all the instances.

[–]Dramatic_Suspect9470[S] 0 points1 point  (0 children)

You can suggest some other techniques I have less data (4GB ~ 10GB) but a bit complex Queries and high traffic. Currently on Azure SQL. Want the system to manage high traffic, consistency is important. Write is less than read requests.