BTUG - Dec 2014 - Hybrid Connectivity Options
•Télécharger en tant que PPTX, PDF•
1 j'aime•629 vues
Slides used to present at BTUG in Belgium
Recommandé
Recommandé
Contenu connexe
Tendances
Tendances (20)
Similaire à BTUG - Dec 2014 - Hybrid Connectivity Options
Similaire à BTUG - Dec 2014 - Hybrid Connectivity Options (20)
Plus de Michael Stephenson
Plus de Michael Stephenson (17)
Dernier
Dernier (20)
BTUG - Dec 2014 - Hybrid Connectivity Options
- 7. SaaS Applications Cloud Platforms Devices & thingsPartners Enterprise Servers Enterprise applications Custom applications Databases Networking & infrastructure Data & intelligence
- 10. 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
- 11. 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
- 12. Will we get training? How do we monitor it? How do we know if its broken?
- 13. 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
- 14. I don’t care I just want to get it done
- 15. Different integration patterns may have different requirements The projects are all doing different things? So many options how do I decide which to use?
- 19. Miami data centre UK data centre Denmark data centre Network provider MPLS network
- 20. 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
- 21. Miami UK SQL Server data warehouse Azure Network SQL Server Integration Services Network provider MPLS network
- 23. Azure Development Lab Active Directory Dev Machine 1 Dev Machine NBuild server UK Developers USA Developers Romanian near-shore team India off-shore team
- 25. Active Directory LOB servers Database servers Mainframe On-premise data centre Azure Network VPN BizTalk IIS application servers
- 27. Denmark data centreAN-OTHER data centre IBM websphere WCF routing service Azure Azure Service Bus Relay Partner Management Application
- 28. My data centrePartner data centre Azure Azure Service Bus Relay Partner Management Application BizTalk
- 30. Azure Business 1 Business 2 API Azure Service Bus BizTalk Websphere
- 31. My data centre Azure BizTalk Azure Service Bus SQL Server
- 33. 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. On-premise data centre Azure BizTalk Services Hybrid Connection Agent Hybrid Connection Endpoint Hybrid Connection Management Azure Websites Website Website
- 37. 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
- 39. Analyze Requirements Produce candidate architectures Compare Architectures Rate Decide Own & Lead
- 40. 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
- 41. 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. 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
- 44. My data centre Problems • Processing logic changes • No channel for “modern claims”
- 45. 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