Multi-region deployments
Last updated:
AZURERESILIENCY
- Mostly active-passive setups but can be active-active too
- because: latency
- because: data consistency
- Deploy to at least 2 regions
- Ensure all core elements are present in both regions
- Some resources can not move between regions (example: public IPs)
- Need to balance between regions
- Azure traffic manager is a solution for this/DNS based
- Azure front door
- creates any cast IP in edge locations
- when client makes request initial sessions it can do in edge
- when request is made it goes to closest region
- Cross region global LB