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 and Central US, with each providing availability to the other. But I feel that users in the west coast may need better coverage with another region deployment to fully blanket the US with a third deployment with East US and West US using Central US for availability and Central US in turn uses either East US or West US for availability. Or should the two region deployment be East US and West US so users in Central US can access either?
Basically, I need best practice suggestions on how to approach covering the entire US with the proper infrastructure for my application. I appreciate it.
3 Replies
- 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! techieg4 I don't have the details for the said application but my take from your question is, you have an internet-facing application with the following requirements:
- This application needs to be accessed across the US over the internet.
- The application will be hosted on IaaS based solution and you already had two region-based architecture and
- You want to know how to ensure coverage for the application across the US.
With the limited information and above assumptions following component can be leveraged to design a solution:
- Azure CDN (To access the content from nearest edge location).
- Traffic Manager (for DNS based routing or HA or DR)
- Application Gateway (for web traffic load balancing and Security - WAF)
or - Front door (Loadbalancing need, HA, DR and security)
or - Opt for PaaS solutions (Web app, queue, function, and DB)
I am not sure if that answers your query, if not please provide more details for your application and requirements for a more precise solution and best practices
- Perhaps combining Application Gateway and Front Door would prove even more useful.
