The Hitchhiker’s Guide to Hybrid Connectivity

Dan Toomey
Integration MVP
The Hitchhiker’s Guide to Hybrid Connectivity

Integrating the DigitalEnterprise

What This Talk is NOT About
• Integration Patterns
– Specifically focuses on connectivity options
– Excludes async patterns (i.e. Service Bus queues / topics)
• Demos
– Theoretical talk only due to time constraints
• Network Level Connectivity
– Mentioned as an option, but not the primary focus
– Concentrates on non-network options

The Hitchhiker’s Guide to
Synchronous Hybrid Connectivity
with
Limited Network Changes

Agenda
• Network Based Options
– VNET Types (P2S, S2S, ExpressRoute)
– VNET Integration
• Non-Network Based Options
– Azure Relay
– On-Prem Data Gateway
• Scenarios

Network Based
Options

Azure Virtual Network
image: https://docs.microsoft.com/en-us/azure/virtual-network/virtual-networks-overview
Types:
– Point to Site (P2S)
– Site to Site (S2S)
– ExpressRoute
P2S, S2S
ExpressRoute

VNET Integration for Web / Mobile Apps
• Requires Standard or Premium
App Service Plan
• VNET must be in same
subscription as ASP
• Must have P2S enabled
• Must have Dynamic routing
gateway
image: https://docs.microsoft.com/en-us/azure/app-service-web/web-sites-integrate-with-vnet

VNET with API Management
• Added layer of security
• All the benefits of APIM
NSG
Corporate Network
Application
Server
BizTalk Server
Database
Server
Virtual Network
API Mgmt
Application
Gateway
VPN
Gateway
NSG
External
Client

Non-Network Based
Options

Relay – An Alternative Approach
• Relay underpins all of the non-network connectivity options
– Azure Relay
• WCF Relay
• Hybrid Connections
– On Prem Data Gateway

Load Balancer
Network Address Translation
Router
H/W FIrewall
S/W FIrewall
Why the Relay?
• Traffic OUT is not usually a problem
• Traffic IN – different story!
Application
Server
Client Network Target Network
Application
Server

Application
Server
Client Network Your Network
Application
Server
Relay
Service
How Relay Works
• Concepts:
– Secured listener endpoint in the
cloud
– Opened via an outbound
connection from within corporate
network
– Clients send messages via the
listener’s endpoint
– No changes to corporate firewall or
network required
• As long as it allows outbound
traffic on
port 80/443

Azure Relay
• Generally Available as of 27 March 2017
• One of the three Service Bus offerings
• Comprised of two services:
– WCF Relay
– Azure Relay Hybrid Connections

WCF Relay
WCF Service
Application
Server
Client Network
Microsoft
Azure
Your Network
WCF Relay – How It Works
• WCF Relay point within a Service Bus namespace
• Outbound connection from an on-prem WCF service
• Uses WCF relay bindings:
– NetTcpRelayBinding
– BasicHttpRelayBinding
– WS2007HttpRelayBinding
– NetOnewayRelayBinding
– NetEventRelayBinding
– WebHttpRelayBinding
– NetMessagingBinding
• Security via Shared Access Signatures (SAS)
• Accessible from a variety of services & locations
BizTalk Server
API Management
Azure
Function
Web App
BizTalk Server

WCF Relay – Constraints
• Needs a self-provided listener
service
• Relies on Windows / .NET
framework
• Optimised for XML messaging
BizTalk Server
API Management
Azure
Function
Web App
BizTalk Server
WCF Relay
WCF Service
Application
Server
Client Network
Microsoft
Azure
Your Network

WCF Relay – Pricing
WCF RELAY PRICING
Relay hours $0.10 for every 100 relay hours
Messages $0.01 for every 10,000 messages
The monthly prices are calculated based on 744 hours of use. Connections will be charged in one hour increments.
MONTHLY USAGE SCENARIO:
1 connection x 744 hours + 1 million messages** = US $1.74*
*Excludes data egress charges
**Message size up to 64KB

Hybrid Connections
• Works at the transport level (web sockets)
• Relies on port forwarding (hostname + port)
• Requires only a Service Bus namespace (no MABS)
• Cross Platform (Windows & Linux)
• Codeless experience for Web Apps / Mobile Apps
• API accessible for other scenarios

Hybrid Connections – How It Works
• Connection created in Azure (Service Bus)
• Hybrid Connection Manager installed on prem
Web App
Mobile App
Corporate Network
Microsoft SQL Server
Hybrid Connection
Other published resources
Hybrid Connection
Manager

Hybrid Connections – Scalability
• Connection created in Azure (Service Bus)
• Hybrid Connection Manager installed on prem
Web App
Mobile App
Corporate Network
Microsoft SQL
Server Cluster
Hybrid Connection
Hybrid Connection
Manager

Hybrid Connections – Using the API
• Port Bridge code option (running as a Windows
service)
Azure VM
Corporate Network
Hybrid Connection
Server
Samples: github.com/Azure/azure-relay-dotnet/

Azure Relay Hybrid Connections
Constraints:
• Maximum 10,000 relay endpoints per namespace
• Maximum 25 listeners per relay
• Best for Azure-hosted clients
• Codeless experience limited to Web/Mobile Apps
– … but plenty of examples of the rest on GitHub!
github.com/Azure/azure-relay-dotnet/

Azure Relay Hybrid Connections – Pricing
HYBRID CONNECTION PRICING
Connection Charge (includes 5 GB of data/month) US $10 per Listener
Data Transfer Overage (Data exceeding the included 5
GB/month)*
US $1/GB
*The data transfer limit of 5 GB covers total data transfer across all listener units.
2 HC listeners + 10 GB data = US $25.00 [ ($10 x 2) + $ 5 data overage ]
3 HC listeners + 100 GB data = US $125.00 [ ($10 x 3) + $ 95 data overage ]

Which Azure Relay to Use?
Hybrid Connections
(TCP, Port Forwarding)
WCF Relay
(WCF Application Stack)
Application
Layer
Transport
Layer

On-Premises Data Gateway
• Generally Available as of 4th May 2017
• Acts as a bridge between Azure PaaS and on-prem
resources
• Works with connectors for Logic Apps, Power Apps,
Flow & Power BI:
• BizTalk Server
• DB2
• File System
• Informix
• MQ
• MySQL
• Oracle Database
• PostgreSQL
• SAP Application Server
• SAP Message Server
• SharePoint for HTTP
only, not HTTPS
• SQL Server
• Teradata

On-Premises Data Gateway – How It Works
• Download and install the gateway
on-premises
• Create and associate a data
gateway in Azure
• Connect Logic App / Power App /
etc to gateway
• Can run over ExpressRoute
26

On-Premises Data Gateway – Constraints
• Accessible only from within managed connectors (no API)
• Only one gateway installed per machine
• Cannot be hosted on a domain controller
• Requires Windows host (Win 7 / 2008 R2 or later)
• Must use Azure school or work account
• No current support for High Availability (but on roadmap)
27

On-Premises Data Gateway – Pricing
ON-PREMISES DATA GATEWAY PRICING
FREE!! (but you pay for the services that use it)
Logic App Action Quantity / month Price Cost
Polling trigger (1 min interval) 43,200 0.0008 $ 34.56
Execution shape (first 250K) 206,800 0.0008 $ 165.44
Execution shape (next 750K) 750,000 0.0004 $ 300.00
TOTAL COST: $ 500.00

Scenarios

Scenario 1: Azure Web/Mobile App to On-Prem
Web App
Corporate Network
?

Corporate Network
Hybrid Connection Hybrid Connection
Manager
Web App

Alternatives:
WCF Relay Point 2 Site
VNET
Logic App +
OPDG
Expose resources at a fine-grained level 
Leverage WCF stack features 
Use Active Directory Authentication X  X
Move large amount of data 
Minimise ongoing cost 

Scenario 2: IaaS Server (VM) to On-Prem
VM
Corporate Network
?

Scenario 2: IaaS Server (VM) to On-Prem
Corporate Network
Hybrid Connection
Port Bridge
ServerVM

Scenario 2: IaaS Server to On-Prem
Alternatives:
WCF Relay Logic App +
OPDG
Site 2 Site
VNET
Use Active Directory Authentication X X 
Move large amount of data  
Leverage managed connector(s) X 

Scenario 3: SaaS Service to On-Prem
Corporate Network
?

Corporate Network
Logic App On-Prem Data
Gateway
OPDG Manager

Alternatives:
API Gateway
w/VNET
WCF Relay Hybrid
Connection
Expose resources at a fine-grained level  
Leverage WCF stack features  X
Move large amount of data  () X
Protocol translation  X
Tracking / Monetization 

Corporate Network
?
Partner Network
Scenario 4: Business to Business

Corporate NetworkPartner Network
Logic App On-Prem Data
Gateway
OPDG Manager
Enterprise Integration Pack
Maps TPMSchemas

Alternatives:
API Gateway
w/VNET
WCF Relay Hybrid
Connection
Expose resources at a fine-grained level  
Leverage WCF stack features  X
Move large amount of data  () X
Protocol translation  X
Tracking / Monetization 

Scenario 5: Service Fabric Cluster to On-Prem
Service Fabric
Corporate Network
?

Corporate Network
Hybrid Connection
Other published resourcesPort Bridge
Server
Service Fabric
{}
{}
{}

Alternatives:
WCF Relay Logic App +
OPDG
Site 2 Site
VNET
Use Active Directory Authentication X X 
Move large amount of data  
Leverage managed connector(s) X 

Use <this> technology when…
VPN • Multiple
resources and
protocols
require
connectivity
• Integration with
a single AD is
required
• High bandwidth
low latency
demands
• Network
reconfiguration
is justified
WCFRelay
• Client is outside
of Azure
• Client is not a
Web Site or
Mobile Service
• Fine-grained
exposure of
WCF services
required
• Desire to
leverage
features of the
WCF stack
• Ongoing costs is
a factor
HybridConnections
• Client is a Web
App or Mobile
App (codeless)
• Target is a port
based
connection to
an application
server
• Connecting to a
TCP resource
that is not .NET
or even
Windows
• Administrators
want fine-
grained control
and auditing
On-PremDataGateway
• A fully PaaS
solution is
desired
• LOB is one of
the supported
managed
connection
types
• Supporting
B2B/EDI via
Logic Apps &
EIP
• Tracking is
required

Cost/Effort Comparison
D
E
V
E
F
F
O
R
T
O N G O I N G M O N T H L Y C O S T
26
4
1
3
5
7
$10 $100 $200 $500 $750 $1000
Dev effort pertains to hybrid integration part only, not application functionality
Scale is non-linear
ID Description Operational Qty/mo
1 WCF Relay 1 relay, 1m msgs
2 OPDG w/Logic App 5x actions, 1 min trigger
3 VNET w/Web App Std ASP S1, 1 Web App
4 VNET w/APIM APIM Std
5 VNET w/APIM & App Gateway & WAF APIM Std, AG Med
6 HC w/Web App 1 listener, 10GB data, Std ASP
7 HC w/VM 1 listener, 10GB data + D2 v2 VM
High
Med
Low

References
• The New Azure Hybrid Connections
https://www.mexia.com.au/the-new-azure-hybrid-connections/
• Hybrid Connectivity Options in the Microsoft Cloud
https://www.biztalk360.com/integrate-2014/hybrid-connectivity-options-microsoft-cloud/
• Why use Service Bus Relay now I have Hybrid Connections?
http://microsoftintegration.guru/2014/07/07/use-service-bus-relay-now-hybrid-connections/
• On-Premises Data Gateway
https://docs.microsoft.com/en-us/azure/analysis-services/analysis-services-gateway
• What Is Azure Relay?
https://docs.microsoft.com/en-us/azure/service-bus-relay/relay-what-is-it
• Understanding Azure Relay
https://www.servicebus360.com/blogs/understanding-azure-relay/
• Azure Relay Samples on GitHub
https://github.com/Azure/azure-relay/tree/master/samples/WCF%20Relay

Pluralsight Course

Let’s connect!
dan@mexia.com.au
@daniel2me
linkedin.com/in/danieltoomey
mindovermessaging.com

The Hitchhiker’s Guide to Hybrid Connectivity

More Related Content

What's hot (20)

Similar to The Hitchhiker’s Guide to Hybrid Connectivity (20)

More from Daniel Toomey (20)

Recently uploaded (20)

The Hitchhiker’s Guide to Hybrid Connectivity

Editor's Notes