Thanks for using the Q&A platform.
Here's a recommended approach using geo-distributed architecture and traffic optimization techniques:
Deploy Regional VMs + Replicated SQL Setup
- Deploy Secondary VM in the UK.
- Clone your application setup and place it close to UK users for lower latency.
- Implement SQL Replication
- Use SQL Server 2022 replication between Southeast Asia and the UK:
- Transactional Replication for near real-time sync.
- Or use Always On Availability Groups if you need read/write on both sides; this requires a Windows Server Failover Cluster.
- UK users read from the UK SQL replica (read-only if needed), Singapore users use the primary.
- Use SQL Server 2022 replication between Southeast Asia and the UK:
- Use Global Load Balancer
Use Azure Front Door to route traffic based on user location (geo-proximity) to the nearest app instance
Kindly find Microsoft documentation for more insight:
https://learn.microsoft.com/en-us/sql/database-engine/availability-groups/windows/configure-replication-for-always-on-availability-groups-sql-server?view=sql-server-ver17
https://learn.microsoft.com/en-us/sql/database-engine/availability-groups/windows/read-scale-availability-groups?view=sql-server-ver17
https://learn.microsoft.com/en-us/azure/frontdoor/
https://learn.microsoft.com/en-us/azure/load-balancer/cross-region-overview
Lastly, host the app in a middle-ground region if managing replication is too complex.
If the response was helpful, please feel free to mark it as “Accepted Answer” and consider giving it an upvote. This helps others in the community as well.
Regards,
Obinna.