More Related Content


Introduction to Hybrid Connections

  1. Microsoft Azure
  2. Microsoft Azure
  3. WCF Relay Bindings Service Bus Partners Microsoft Azure
  4. BizTalk Adapter Svcs BizTalk Services Partners Microsoft Azure
  5. Web Sites Mobile Services Corporate Network Microsoft SQL Server Hybrid Connection Other published resourcesHybrid Connection Manager
  6. Multiple applications can share a Hybrid Connection to access an on-prem resource Applications on Azure access a resource the same way they would if it was running on-premises Hybrid Connection Hybrid Connection Manager
  7. Multiple instances of the Hybrid Connection Manager can be used on-premises for resiliency and load-balancing. Hybrid Connection Hybrid Connection Manager
  8. Free Developer Basic Standard Premium Price $0 / month ~$97 / month ~$499 / month ~$2,999 / month ~$5,997 / month Scale Limit N/A N/A Up to 8 units Up to 8 units Up to 8 units EAI Bridges per Unit N/A 25 25 125 500 EDI Agreements per Unit N/A 10 50 250 1000 Hybrid Connections per unit 5 5 10 50 100 Hybrid Connection data transfer per unit 5 GB 5 GB 50 GB 250 GB 500 GB Archiving N/A Included Not Included Not Included Included High Availability Not Included Not Included Included Included Included Connection limits for each Hybrid Connection apply. Additional Hybrid data transfer billed at $1/GB.
  9. Announcing Hybrid Connections: Building Amazing Hybrid Web Sites & Mobile Apps in Minutes Hybrid Connections (Preview) Hybrid Connections Overview Create and Manage Hybrid Connections
  10. Why Use Service Bus Relay Now I Have Hybrid Connections? Using Hybrid Connections to Consume an On-Premises WCF Service from the Cloud Santosh Chandwani Microsoft Program Manager, Azure Email: Twitter: @santoshc1 Dan Toomey Consultant, Mexia | Azure Advisor Email: Twitter: @daniel2me

Editor's Notes

  1. Excited about this because implications from an integration perspective are far-reaching.
  2. Gave initial presentation at TechEd USA when this went live in preview
  3. MS understands that it’s neither practical or beneficial to move “everything” to the cloud. Strategy is to bring computing resources to your enterprise to extend your capabilities.
  4. First is at the infrastructure level: Atom bomb of integration Allows use of AD, Windows Authentication, etc. Cons: Security? Overkill?
  5. More targeted approach: Provides a great environment for running web apps and public facing services. Also a great “DMZ” for connecting with partners. Cons: Dependency on .NET, WCF, IIS, AppFabric No direct line to LOB systems Needs custom code
  6. Along came BizTalk Services – PaaS Integration Adapters work OOTB with LOB systems Hosted in IIS. Cons: Requires MABS
  7. Microsoft’s goal as a platform is to offer our customers AGILITY and FLEXIBILITY. Build as fast as possible Enable a broad spectrum of integration Eliminate security concerns due to network re-configuration Allow for finely-grained control of access to resources
  8. To date, fastest way to integration Azure Websites & Mobile Services Hopefully will extend to other Azure services Currently in preview Part of MABS
  9. Whole new tier introduced in MABS
  10. If it uses TCP to connect, should work No dependency on .NET framework (transport level) Like SB, no network changes req’d Give finely grained control over access to resources
  11. Can add multiple connections & services… which leads to next slide
  12. We could do more by supporting delegation of Hybrid Connection Management.
  13. Recap: Lift your existing on-premises app straight to the cloud No custom code req’d Completely a configuration-driven experience