tSponsors

Jon FanceyIntegration MVP, Author

Migrating to Microservices

BizTalk Summit 2015 – LondonExCeL London | April 13th & 14th

Dan ProbertAffinusLabs

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

What we’ll coverRecap on last year

Mapping from BizTalk Server to the new world

Practicalities of migration

Tooling

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

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

The ChallengeBizTalk Server architecture

◦ Ports

◦ Pipelines

◦ Maps

◦ Orchestration

◦ Rules

◦ Adapters

◦ EDI TPM

◦ BAM, Tracking

◦ Oh my!

MappingMapping 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)

BRERules API App◦ Portal-based designer

Similar concepts as BizTalk Server◦ RETE engine

◦ Vocabularies and Policies

Facts - currently support for:◦ XML and literals

Trading partner managementImportant 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

BizTalk pipeline vs Logic AppProcess stages map to API Apps

Custom processing via APIs

Custom processing via pipeline components

PipelinesExecution 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

Wouldn’t it be great…IF A COMPANY WAS ALREADY WORKING ON THIS PROBLEM?

Introducing…The Migration Factory

In exclusive partnership with Microsoft

Fully-automated approach to migration

With help if you need it

The migration workflowExport

◦ MSI from BTS

Upload◦ MSI to The Migration Factory

Parse◦ Generated report

Pay/Collect◦ Convert, package and deploy

Export MSI

Upload Parse

Generate Report

Accept

Payment Convert

Deploy

You Us

DemoMigrating pipelines to Logic Apps

Product ScopeEverything

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)

Orchestration migrationHard 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’

But BizTalk is more than thisSupport 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

Finally… BAM / TrackingOk 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

Where are we?

BizTalk Feature MABS Feature/Alternative Support

Maps Transform Good

Schema Schema Good

Pipelines Logic App Good*

Adapters Source/Destination OK

Orchestration Logic App OK/Tough

BRE API App Good/OK#

BAM / Tracking Tracking OK

Trading partner mgmt. Trading partner mgmt. Good

*unless Tx

# db / custom

We want your feedbackRegister your interest at

www.themigrationfactory.euPricing 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?

SummaryMigrating 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

Thanks!

Any questions, follow up –

@jonfanceyhttp://www.jonfancey.comjon.fancey@affinus.co.uk

@probertdanielhttp://www.bizbert.comdan.probert@affinus.co.uk