Architecture - Page -1
Enterprise Architecture (End-to-End)
Users Worldwide
│
▼
Azure DNS (Custom Domain)
│
▼
Azure Front Door (Global WAF, CDN, Routing)
│
▼
Microsoft Global Backbone Network
│
┌───────────────────┼───────────────────┐
▼ ▼ ▼
East US West Europe Southeast Asia
│ │ │
▼ ▼ ▼
Application Gateway Application Gateway Application Gateway
(Regional WAF) (Regional WAF) (Regional WAF)
│ │ │
▼ ▼ ▼
Internal Load Balancer Internal Load Balancer Internal Load Balancer
│ │
┌────┴────┐ ┌────┴────┐ ┌────┴────┐
▼ ▼ ▼ ▼ ▼ ▼
AKS VMSS AKS VMSS AKS VMSS
│ │ │ │ │ │
└────┬────┘ └────┬────┘ └────┬────┘
▼ ▼ ▼
Microservices Microservices Microservices
│ │ │
▼ ▼ ▼
Azure SQL / Cosmos DB / Storage (via Private Endpoints)
│
▼
Monitoring & Operations
Azure Monitor • Log Analytics • Application Insights
Microsoft Sentinel • Azure Backup
│
▼
Administration Plane
Azure Portal → Azure Bastion → Private VMs
Users
USA
Europe
Asia
Australia
Africa
South America
│
▼
=========================================================
Azure Front Door (Global Service)
=========================================================
Microsoft Edge POPs (Hundreds of Locations Worldwide)
Examples:
USA
├── New York
├── Chicago
├── Dallas
├── Seattle
└── Los Angeles
Europe
├── London
├── Amsterdam
├── Paris
├── Frankfurt
└── Madrid
Asia
├── Singapore
├── Tokyo
├── Seoul
├── Hong Kong
├── Mumbai
└── Jakarta
Australia
├── Sydney
└── Melbourne
Middle East
├── Dubai
└── Qatar
Africa
├── Johannesburg
└── Cape Town
South America
├── Sao Paulo
└── Santiago
(All are Microsoft Edge POPs)
│
▼
Microsoft Global Backbone Network
│
▼
Regional Azure Deployments
✔ Types of Azure Load Balancer
Azure Load Balancer comes in 2 modes:
1. Public Load Balancer
- Exposed to internet
- Has public IP
- Used for external traffic (rare if you use Front Door + App Gateway)
2. Internal Load Balancer (ILB) ⭐
- Private IP only (RFC1918)
- Used inside Virtual Network
- Not reachable from internet
- Used for microservices, backend tiers, AKS internal services
Comments
Post a Comment