Transcript Building Highly Available and Scalable Applications in

Global scale with
Microsoft Azure
Scenarios
Achieving high
availability with Microsoft
Azure
Demos
ExpressRoute
Virtual Network
S2S and P2S VPN
Traffic Manager
DNS
Network Services
Core
SDN tech
Network Manager
Virtual Network
Infrastructure
Software
Load Balancer
Virtual Switch
Network APIs
Logical Network
Uniform
shared
network
Network Topology
Network Hardware
Automation
Network Monitoring
Physical Network
NIC Performance
Offloads
Security, Compliance
Network
services
www.yourapp.com
Performance - Direct to “closest” service based on network latency
Round-robin - Distribute equally across all services
Failover - Direct to “backup” service if primary fails
—also included in other policies
www.yourapp.com
Performance - Direct to “closest” service based on network latency
Round-robin - Distribute equally across all services
Failover - Direct to “backup” service if primary fails
—also included in other policies
DNS (Domain Name System) based global
traffic management
Traffic Manager profile created with name
(contoso.trafficmanager.net), routing policy,
and health monitoring configuration
Service instances (endpoints) then added to
the Traffic Manager profile to route traffic
between those services
Traffic Manager supports IaaS VMs, PaaS
Web/Worker roles, Azure Websites and
Non-Azure endpoints as peers in the same
profile with active monitoring for all
endpoints
CNAME
a.root-servers.net
…
k.root-servers.net
1
2
Q: What is www.contoso.com?
A: Ask ns1/2.contoso.com
ns1.contoso.com
ns2.contoso.com
3
4
Q: What is www.contoso.com?
A: CNAME to contoso.trafficmanager.net
contoso.trafficmanager.net
Which deployments are up?
A: 11.22.33.44
Users’ LDNS
IP=99.88.77.66
What are the regions for
deployments A and B?
What is the network distance
between IP 99.88.77.66 and
the US North and West Europe
regions?
“choose the best performing
deployment” between:
Deployment A
Deployment B
Deployment C
Microsoft
Azure
<subnet X>
<subnet Y>
<subnet Z>
DNS Server
Virtual Network
Global Connectivity
Connect to multiple on-premises
locations
Global private network
Contoso NorthAm HQ
(10.0.0.0/16)
Contoso East Asia
(10.3.0.0/16)
Azure Load
Balancer
Cloud
service VIP
IP: 127.255. ---.---
IP: 127.255. ---.---
IP: 111.111. ---.---
IP: 101. 121.---.255
IP: 101. 121.---.255
IP: 2001:4898:9:2:--:e60c:b118:---
22
Internal load balancing (preview)
Internal Load balancing (ILB)
between VMs without public facing
endpoints
Enables load balancing among VMs
with private IP addresses
Load balanced endpoint accessible
only by customer’s virtual and
on-premises networks or just
within the cloud service
External
load
balancer
Internal VIP
Internal
load
balancer
Web frontend tier
Logic tier
Customers from
VNet & On-Prems
Client
VNet
Contoso US HQ
Contoso East Asia
Today, every cloud service gets a VIP
(public virtual IP address) assigned by Azure
Instances and VMs inside a cloud service
get private IP addresses. These VMs only accessible via
endpoint port mapping
from VIP to the VM.
LB
Cloud service
Reserved VIP
VM1
DIP1
VM2
DIP2
VIP: <port x>  DIP1:<port y> OR DIP2:<port y>
Today, every cloud service gets a VIP
(public virtual IP address) assigned by Azure
Instances and VMs inside a cloud service
get private IP addresses. These VMs only
accessible via endpoint port mapping
from VIP to the VM.
instance level public IPs
Cloud service
Reserved VIP
Load
Balancer
DIP1
DIP2
Internet
Microsoft Engineering
Stories
http://www.visualstudio.com
Visual Studio
Industry Partner
Program
Visual Studio | Integrate