This document discusses hybrid connectivity options with Microsoft Cloud. It provides an upcoming events schedule for webinars on topics like Azure API Management, BizTalk, healthcare integration, and Azure services. It also includes diagrams showing different hybrid architectures using technologies like Azure, BizTalk, Service Bus, and VPNs. Key considerations for different options are discussed, like requirements, skills needed, costs, and organizational benefits. Overall it explores various ways to integrate on-premises systems with Azure and leverage technologies like BizTalk and Service Bus.
1. Sponsored & Brought to you by
Hybrid Connectivity Options with the
Microsoft Cloud
Michael Stephenson
https://twitter.com/michael_stephen
https://www.linkedin.com/in/michaelstephensonuk1
2. Upcoming Events
Date Speaker Title
16th Feb Josh Twist Azure API Management Product Team Update
23rd Feb Steef Jan Wiggers BizTalk extensibility
3rd March Howard Edidin BizTalk on Fhir – Developing HL7 Fhir Solutions with BizTalk
9th March Ramraj Rajkumar Healthcare Integration | Opening the Doors to Communication
16th March Sami Tahtinen From ground to interstellar - how to expand EAI to multiple organizations?
23rd March Tomasso Groenendijk Modifying and Extending the ESB Toolkit
30th March Dan Rosanova Azure Service Bus Team – Product Update
6th April Nino Crudele Azure Event Hubs
Currently have events lined up well into June… watch this space!!
11. I want a
strategic
solution
I want
something
reusable
I want value
for money Minimize
complexity
I want to
deliver for my
customers
Can I put
everything in
the cloud and
save loads of
money
12. We are
comfortable
with VPN
Will we get
training on
anything
new?
If its not
servers how
do we
manage it?
We are
concerned
about
security
14. I want a
chance to
play with new
things
There’s loads
of ways I can
do this
I don’t want to
be blocked so I
can hit my
deadlines
Look it works
on my
machine and
its easy
16. Different integration
patterns may have
different
requirements
The projects are all
doing different
things?
So many options
how do I decide
which to use?
17.
18.
19.
20. Miami data centre
UK data centre Denmark data centre
Network provider
MPLS network
21. Sync’d Read only copy
of AD
Active Directory Active Directory
LOB servers
BizTalk
IIS application servers
Database servers Mainframe
BizTalk
LOB servers
IIS Application servers
Database servers
On-premise data centre Azure Network
Network provider
MPLS network
24. Azure Development Lab
Active Directory Dev Machine 1 Dev Machine NBuild server
UK Developers USA Developers
Romanian near-shore team
India off-shore team
34. On-premise data centre
BizTalk Adapter Service
On-premise Agent
BizTalk Adapter Pack
LOB Adapters
BizTalk Services
EAI Bridge
BizTalk Adapter Service
Endpoint
BizTalk Adapter Service
Management
Mobile device
35.
36. On-premise data centre
Azure BizTalk Services
Hybrid Connection
Agent
Hybrid Connection
Endpoint
Hybrid Connection
Management
Azure Websites
Website
Website
37.
38. My Data Centre
Azure
BizTalk
WCF Service
Options I could choose
1. Site to Site VPN
2. Express Route
3. Azure Service Bus Relay
4. BizTalk Hybrid Connections
BizTalk needs to
query data via WCF
service
41. Design
• How does it fit with my architecture
• Will it solve the problem
• Will it perform
• Is it secure
Delivery
• Can my development team work with this
approach
• Can I do a proof of concept
Operations
• Do my team have the skills to manage
• Do we need new tools
Organisation
• Are there organisational benefits to the
approach (eg: Reuse)
• Is it expensive
There’s loads of factors for consideration discussed in the book
42. Technology Design Delivery Operations Organisation
Express Route 9 0 8 6
Site to Site VPN 8 5 7 8
Service Bus Relay 7 9 8 7
Hybrid
Connections
7 6 7 6
43.
44. Azure
Microservice 1 Microservice 2 Microservice 3
My data centre
Service BusBizTalk Services
Hybrid Connections
BizTalk Adapter
Service
?
• MABS 1.0 is production ready
• Will these features migrate to Microservices
Connectors
• Expect a clean migration story
• Should be safe
46. Azure
Claim Processing Microservice 1
My data centre
Service Bus
API Validate Approval Publish
Benefits:
• Isolate what changes frequently
• Use BizTalk Server for the batch processing
• Use BizTalk Server for LOB integration
• Combine Service Bus & BizTalk for Throttling
• Expose Microservice API to new Consumers
• Autoscale where we need to, throttle where we don’t
• REUSE, REUSE
Notes de l'éditeur
If we have an existing MPLS network with out network provider then we can work with the network provider to add Azure so it appears like another site on the WAN
By adding Azure to the MPLS network servers in Azure just appear like any other server on the WAN.
We can create a read only copy of AD in Azure to improve performance
Extended data centre opens up lots of opportunities for cloud hosted IaaS
Burst load
Dev / Test environments
Backup
Hardware reduction
Infrastructure cost saving
SQL Data Warehouse in Azure to support large scale compute based BI
How do we get the data to the data warehouse?
We wanted to bulk load data from databases in each site to a cloud hosted SQL Data Warehouse
MPLS network allows SSIS to reach the databases in each site
Express Route allows us to pull large amounts of data with good bandwidth
We were creating a global BizTalk development environment hosted in Azure
Most developers were easily able to access VM over public internet
In UK on premise restrictions stopped us doing that
Point to Site VPN was used to tunnel over HTTP using SSTP allowing developers to connect the VPN software and access VM
Customer moving infrastructure to cloud
BizTalk was being upgraded and they wanted to host new version in the cloud
BizTalk still needed to access many resources on premise with no significant re-development
This is also great for dev/test scenarios and temporary environments
Why did we choose Relay and not VPN
Cost
Setup Time
Fewer infrastructure challenges
Fail fast & Cheap
Don’t have to worry about controlling access to other resources, the endpoint is the only resource
Can easily expose to other consumers
Why not just expose the services publically
I don’t need to worry about my DMZ
I don’t need to worry about DOS
I don’t need extra infrastructure
Why did we use WCF Routing Service
Allowed us to expose non Microsoft technologies
Routing Service can forward calls to another web service
WCF Routing Service was a simple listener
We can control which services are exposed via routing rules
If you’re a BizTalk customer and you want to expose your integration processes in BizTalk outside of your organisation then Service Bus Relay is probably the easiest way you can do this.
Key Benefits
Decoupled architecture with API not aware of each business
Supports publish / subscribe pattern
One way and two way messaging
Plug in new business units
In this example BizTalk is using a SQL Query to get some recent changes, debatches them and then publishing event messages for each change
Service Bus Queues support a good on-premise to cloud integration pattern
Queues are a good way to deal with high volume event publishing
Receivers can be inside the organisation or outside of it
Key Benefits
Low cost
No infrastructure requirements
Queue is PaaS so can be accessed from anywhere
Supports the Pull based integration pattern
BizTalk Adapter Service is really about taking advantage of the LOB Adapter SDK + BizTalk Adapter Pack but in Cloud Scenarios
The Key benefits are around the simplicity for connecting to LOB applications
We chose the BizTalk Adapter Service because of the specialist capabilities for connecting to SAP or any other application we need to connect to
In the scenario we move the website to the cloud
We still need to connect to the on premise oracle data base
If we set up BizTalk Services Hybrid Connections we are able to reach through to the Oracle Database
We are unlikely to need to change any code our ODP.net code would be routed through hybrid connections simply by changing the connection string
Key Benefits
Migrate to the cloud with potentially no code changes
Can support almost any port so its open for a wide range of connectivity types
Lower level of abstraction than Service Bus Relay which is WCF this can be any port
Word of Caution
Your application authorization model may be affected if your no longer on premise
Lets take a look at a sample
We have BizTalk in the cloud wanting to call an on Premise WCF Service, which choices do I have?
[ASK AUDIENCE TO SEE WHAT PEOPLE THINK]
Key Points
Express Route wasn’t something we already had available so setting this up for this small initiative was a show stopper
Hybrid Connections was at a port level so could be used by more protocols but isn’t GA yet so the SLA was an issue for us
We had used Service Bus Relay many times it was something we were comfortable with in all areas around the business. Its restricted to WCF though
The local infrastructure team are new to Azure infrastructure and setting this up and the learning curve was too steep for initial project but there is an activity to introduce this for projects down the line because there are organisational benefits for other projects