Forum Discussion
Coast-to-Coast Architecture
I am trying to design an architecture for US cost-to-coast application using Azure IaaS and was wondering what the best practice is. I know there is the classic two region deployment, such as Est US ...
Either you could use cross region load balancer to orchestrate the traffic between the two regions. In this case you'll have the two Azure regions receive traffic at the same time. Or, you use Azure DNS, and in this case you'd have a primary region that handle 100% of the traffic and in case of a disaster, with a help of Azure DNS failover, it's going to automatically shift the traffic from the primary region to the secondary region.
Application Gateway operates at layer-7 while Azure Load Balancer operates at layer-4. Application Gateway directs traffic to different routes i.e. images server. While Azure Load Balancer distributes traffic evenly across the registered endpoints.
Hope this helps!
Application Gateway operates at layer-7 while Azure Load Balancer operates at layer-4. Application Gateway directs traffic to different routes i.e. images server. While Azure Load Balancer distributes traffic evenly across the registered endpoints.
Hope this helps!