BizTalk Summit 2015: Migrating to Microservices

1. BizTalk Summit 2015 – London ExCeL London | April 13th & 14th Jon Fancey Dan Probert AffinusLabs Integration MVP, Author Migrating to Microservices t Sponsors

2. Who are we? • @jonfancey • 10-time Microsoft MVP • Wrote ‘THE’ book on MABS – but we won’t talk about that • @probertdaniel • 15-years of crazy BizTalk projects • BizBert

3. What we’ll cover • Recap on last year • Mapping from BizTalk Server to the new world • Practicalities of migration • Tooling

4. Recap - Why move? • Cloud economics • Lower cost • Flexibility – PAYG, scale up/down – provision in minutes - not weeks/months • iPaaS • Less management, server patching, etc • Auto-update of API Apps (if you want it) • Integration is changing • New targets, services • Modern development, faster delivery • Citizen integrator • (Enterprise) integration is too hard – many problems are not central to what you need to do • Why not? • For B2* integration is externally facing anyway – so move compute to cloud • And for EAI platform is coming to you via Azure Pack

5. Recap – So what changed? • Replatform of BizTalk Services • Broken out into API apps • Mapping • Rules • Validation • Flat file processing • Adapters • .. • No longer Windows workflow based • Workflow now implemented as Logic App • We are going to need a new book 

6. The Challenge • BizTalk Server architecture • Ports • Pipelines • Maps • Orchestration • Rules • Adapters • EDI TPM • BAM, Tracking • Oh my!

7. Mapping Mapping is fundamental to integration BizTalk Server maps != BizTalk API Apps Transforms • But Still schema based and XML schema fully supported Three approaches • Maps in BizTalk Server are ‘just’ XSLT much of the time (trfm supports this) • Maps can be converted to transform trfm files using Microsoft-provided tool • Maps can be hosted as-is using Api App – could even use XSLT 2.0  Download the MABS SDK • Command line map conversion tool • VS designer – upload trfm files (same with schema validation)

8. BRE • Rules API App • Portal-based designer • Similar concepts as BizTalk Server • RETE engine • Vocabularies and Policies • Facts - currently support for: • XML and literals

9. Trading partner management • Important for EDI – nobody wants to re-key config for 5000 trading partners • Need the ability to move definitions of trading partners and agreements to cloud • We’re working with the product group to provide for similar migration experience as MABS • E.g. BizTalk Server > TPM conversion > Azure DB > TPM App

10. BizTalk pipeline vs Logic App • Process stages map to API Apps Custom processing via APIs Custom processing via pipeline components

11. Pipelines • Execution model for Logic Apps maps nicely to pipelines • Sequence of operations • Conditional execution • Ability to spin over previous step output – (dis)assembly • Hooking up to Service Bus queue/topic semantic provides persistence, pub-sub, load-levelling, etc. • Custom pipeline components are converted to logic apps • Logic apps have “at least once” semantics • Some things are different • No transactions • Message type must be specified not determined

12. Wouldn’t it be great… If a company was already working on this problem?

13. Introducing… • The Migration Factory • In exclusive partnership with Microsoft • Fully-automated approach to migration • With help if you need it

14. The migration workflow Us You Export MSI • Export • MSI from BTS • Upload • MSI to The Migration Factory • Parse • Generated report • Pay/Collect • Convert, package and deploy Parse Upload Accept Generate Report Payment Convert Deploy

15. Demo • Migrating pipelines to Logic Apps

16. Product Scope • Everything • But we know that some things are harder than others • Gaps & Differences • So it won’t be ‘everything’ – but as close as we can get • Some BizTalk ‘features’ are more popular than others • Importance of the parse/report stage is to provide a “to do” list of actions • We currently understand the syntax and some semantics • Structural conversion of • Maps (and bring schema along), Rules, Pipelines (and pipeline components) • Orchestration to our target* (more in a moment)

17. Orchestration migration • Hard problem to solve – either way • Often used, often unnecessarily  • Logic Apps architecture fundamentally different to BizTalk Server • Execution is partly explicit / partly inferred – e.g. parallelization • Many orchestration features are there but different e.g. IF/THEN/ELSE, retries, etc • Plans • We already parse out ODX files • We are able to target multiple formats depending on complexity • ODX > Logic App • Expression shapes become API apps (Simple Expression shapes become built-in function calls) • ‘as a service’

18. But BizTalk is more than this Support for many messaging patterns • Request-Reply / Solicit-Response • Correlation • Content/Context-based routing • Convoys, Scatter/Gather, Fork/Join flows Logic / API Apps have different characteristics • Not transactional – provides ‘at least once’ • Latency profile different Many messaging patterns are easily identifiable through parsing analysis • And we will provide solutions for as many as we can as well as with the product group as well

19. Finally… BAM / Tracking • Ok there’s no BAM • But it’s unlikely lack of BAM will stop your solution from working • Rare to take dependencies on data in BAM as part of a solution – but possible of course • Logic Apps provides tracking infrastructure • REST APIs to access tracking and archived content • Don’t forget that • BAM is an API and set of tables (with some smart time sequencing etc) • You can interact with API remotely simply with web services • So you could continue to use BAM as licensed BizTalk customer

20. Where are we? *unless Tx #db / custom

21. We want your feedback • Register your interest at • www.themigrationfactory.eu • Pricing models • T-shirt sizes: S/M/L • Fraction of cost of manual conversion • Do if for / with me • Automated self-service • Billed to subscription? • Priorities • What kind of integration applications do you have?

22. Summary • Migrating BizTalk solutions to Logic Apps is possible • Many areas are straightforward • Others are more challenging • But we will do as much as we can, roadmap will plug gaps • Thinking outside the box can help • You can achieve same requirement in a different way, e.g. conditions, parameters • Talk to us , planning on releasing our tools later this year

23. Thanks! • Any questions, follow up – • @jonfancey • http://www.jonfancey.com • jon.fancey@affinus.co.uk • @probertdaniel • http://www.bizbert.com • dan.probert@affinus.co.uk