xsltbiztalkbiztalk-2013biztalk-mapper

BizTalk map functoid vs BizTalk map xslt


I am using BizTalk MAP and inside BizTalk map I am using table looping, table extractor, Scripting, looping functoids.

The same can be achieved in BizTalk map by referencing XSLT.

so Performance wise, which method would be better using BizTalk Map or BizTalk map referencing XSLT.


Solution

  • In fact, your visual BizTalk map created with the BizTalk mapper, is XSLT. Only your functoids are libraries/functions which may be either XSLT or inline C# code. One way you can check this is to right click your .btm map and click 'validate'. In the output window, you will see the link to your XSLT file.

    Performance is very tricky with XSLT. You can write your XSLT in a very good way or in a way that it's not meant to be used. For a pretty basic mapping, performance differences will be there, but will be pretty minor (if any at all). As Dijkgraaf says: the only way to check this, is to test it.

    If your current implementation gives you performance issues, try writing it purely into XSLT, which is very optimized either way. Try taking different approaches/techniques.

    In general, I would always recommend writing XSLT instead of using the mapper, but let's be honest: this is personal preference. I wrote a blog post on this, check it out here: https://pvandenheede.wordpress.com/2016/09/20/the-case-for-xslt/