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 ...
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.
