Stephen W Thomas Using BizTalk Server as your Foundation to the Clouds Azure Hybrid Integration Architect Using BizTalk Server as your Foundation to the Clouds
About Me Consulting for almost 20 years Working with BizTalk Server since 2001 Working with Logic Apps for over 2 years 13 year Microsoft MVP Stephen@StephenWThomas.com @StephenWThomas
Learn Logic Apps Pluralsight QuickLearn Hands-on labs Azure Logic Apps: Getting Started Azure Logic Apps: Fundamentals Plus BizTalk courses Email me for 30-day trial code: Stephen@StephenWThomas.com QuickLearn Week long instructor led course Cloud-Based Integration Using Azure Logic Apps Hands-on labs http://www.StephenWThomas.com/Labs
Session Layout Phase 1 – Why BizTalk and Logic Apps INTEGRATE 2018 Session Layout Phase 1 – Why BizTalk and Logic Apps Phase 2 – Friction Factors
Phase 1 – Why BizTalk & Logic Apps
Why? Not for all scenarios Use connectors not included with BizTalk 100% on premise Low latency No plans to ever do anything outside of the data center Use connectors not included with BizTalk Reduce the load on current BizTalk Servers Plan for the future Save hardware and software costs “be cool like the .Net guys”
How? On-premise data gateway Service Bus queues Logic Apps Adapter API calls
Scenario – Need Connector Social media monitoring (use with Cognitive Services)
Scenario – Need Connector Social media monitoring Customer communications
Scenario – Need Connector Social media monitoring Customer communications Cross team communication
Scenario – Need Connector Social media monitoring Customer communications Cross team communication Incident management
Scenario – Batching Logic Apps does batching really, really well! BizTalk… not so much Logic App batching on any combination of Message Count Batch Size Time Limit of 5k messages or 80 MB
Scenario – Batching Demo
Scenario – Mapping Near seamless execution between BizTalk and Logic Apps Call inside Integration Accounts* or via Azure Functions Database and Custom functoids need to be re-worked Support for custom .Net assemblies
Scenario – Mapping Near seamless execution between BizTalk and Logic Apps Call inside Integration Accounts* or via Azure Functions Database and Custom functoids need to be re-worked Support for custom .Net assemblies See: Migrating BizTalk Maps to Azure Logic Apps: Shortcomings & Solutions
Scenario – Inbound De-batching BizTalk does a good job about inbound de-batching Logic Apps support auto-shredding JSON and XML Not all Logic App triggers and scenarios support Debatching Like a Request-response process
Scenario – Inbound De-batching Demo
Scenario – Inbound FTP/sFTP Use Logic App triggers to receive files Map, de-batch, and log as needed Send to BizTalk for on-prem processing
Scenario – Replace Reverse Proxy Use Logic App to collect inbound data Map, de-batch, and log as needed Great for one way scenarios Front with API Management for more flexibility
Phase 2 – Friction Factors
We Already Have BizTalk
We Already Have BizTalk For all the reasons we have already talked about
Data is too Sensitive
Data is too Sensitive True in some scenarios Use Logic Apps for non-sensitive workloads Do you trust your IT security team or Microsoft more?
Infrastructure Manager says NO
Infrastructure Manager says NO Get the infrastructure team on board early is key You will bother them less No new servers are needed Might reduce on-premise servers Show them all the cool IaaS features Let them feel important and tell them you will make them a co- admin on the Azure Subscription (usually Infrastructure or Ops own the Production subscription with no developer access)
Infrastructure Manager says NO
Learning Curve for Logic Apps If you have worked with BizTalk, Logic App will just make sense
Learning Curve for Logic Apps If you have worked with BizTalk, Logic App will just make sense “Logic Apps is so easy we do not need to hire outside consultants like Stephen anymore”
Learning Curve for Logic Apps If you have worked with BizTalk, Logic App will just make sense “Logic Apps is so easy we ALMOST do not need to hire outside consultants like Stephen anymore”
Azure Changes to Frequently Great! New features Things are made easier JITA Just In Time Architecture
CEO/CTO Says NO to the Clouds
CEO/CTO Says NO to the Clouds
Thanks – Stephen@StephenWThomas.com