locked
Biztalk vs .net RRS feed

  • Question

  • I usually get a question from .net colleagues like why cannot use  .net to receive xml messages and send to certain destination instead of biztalk?

    can anybody explain in highlevel what makes biztalk great than .net ?

    thanks in advance.

    Wednesday, February 22, 2017 11:10 PM

Answers

  • Because .Net is a Framework and collection of languages.  BizTalk Server is a full integration platform.

    While you can do an integration app with just c#, you would have to write every component yourself.

    It the time it would take to write a parser for a simple Flat File, your BizTalk app would be done.

    Wednesday, February 22, 2017 11:34 PM
    Moderator
  • Hi,

    BizTalk is an enterprise level integration product, .NET is not.

    You can read the pros and cons here: A Comparison of Node-building using .Net vs. BizTalk as they are the same across different integration requirements.

    By using BizTalk, you will get all the benefits of using BizTalk – a server product for integration rather using an .NET applicaion or ASP.NET web application. Benefits like

    Tracking – If you want to enable tracking or logging using ASP.NET you have  to create a custom tracking code/library to achieve it but in BizTalk, tracking can be enable much with an  ease.

    1) Health monitoring – Monitoring the status of you process and be done easily using Admin console whereas in ASP.NET you need custom code.
    2) Performance monitoring – With various performance counters specific to BizTalk you can easily manage/monitor the performance of your system.
    3) Throttling – When you have high throughput or when the web/wcf service is being put under heavy load, BizTalk have a build-in capability to throttle the process automatically. In ASP.NET you have to create a complex custom code.
    4) Memory management
    5) Secure Configuration management
    6) Failed message management
    7) Service Isolation
    8) Failover capability
    9) Load Balancing
    10) Disaster recovery

    But as said, BizTalk is a server product and does provide various advantages for integration as a message broker.


    Rachit Sikroria (Microsoft Azure MVP)

    Wednesday, February 22, 2017 11:48 PM
    Moderator
  • Hi,

    BizTalk is a Integration Product and File adapter is  one of the adapter in BizTalk ,You can use multitude of enterprise connectors with BizTalk   like SAP ,Oracle ,SQL ,WCF ,JD Edwards etc without writing any custom code to achieve your task .

    What will happen if there is exception in your .net code  or downstream system is down might be you can log the message and try it process them later . With BizTalk you are automating these manual task like retry ,fault handling and the list is long . BIzTalk also works good with long running transaction ,keep these consideration while working with BizTalk .

     


    If this answers your question please mark it accordingly. If this post is helpful, please vote as helpful by clicking the upward arrow mark next to my reply

    Wednesday, February 22, 2017 11:56 PM

All replies

  • Because .Net is a Framework and collection of languages.  BizTalk Server is a full integration platform.

    While you can do an integration app with just c#, you would have to write every component yourself.

    It the time it would take to write a parser for a simple Flat File, your BizTalk app would be done.

    Wednesday, February 22, 2017 11:34 PM
    Moderator
  • Hi,

    BizTalk is an enterprise level integration product, .NET is not.

    You can read the pros and cons here: A Comparison of Node-building using .Net vs. BizTalk as they are the same across different integration requirements.

    By using BizTalk, you will get all the benefits of using BizTalk – a server product for integration rather using an .NET applicaion or ASP.NET web application. Benefits like

    Tracking – If you want to enable tracking or logging using ASP.NET you have  to create a custom tracking code/library to achieve it but in BizTalk, tracking can be enable much with an  ease.

    1) Health monitoring – Monitoring the status of you process and be done easily using Admin console whereas in ASP.NET you need custom code.
    2) Performance monitoring – With various performance counters specific to BizTalk you can easily manage/monitor the performance of your system.
    3) Throttling – When you have high throughput or when the web/wcf service is being put under heavy load, BizTalk have a build-in capability to throttle the process automatically. In ASP.NET you have to create a complex custom code.
    4) Memory management
    5) Secure Configuration management
    6) Failed message management
    7) Service Isolation
    8) Failover capability
    9) Load Balancing
    10) Disaster recovery

    But as said, BizTalk is a server product and does provide various advantages for integration as a message broker.


    Rachit Sikroria (Microsoft Azure MVP)

    Wednesday, February 22, 2017 11:48 PM
    Moderator
  • Hi,

    BizTalk is a Integration Product and File adapter is  one of the adapter in BizTalk ,You can use multitude of enterprise connectors with BizTalk   like SAP ,Oracle ,SQL ,WCF ,JD Edwards etc without writing any custom code to achieve your task .

    What will happen if there is exception in your .net code  or downstream system is down might be you can log the message and try it process them later . With BizTalk you are automating these manual task like retry ,fault handling and the list is long . BIzTalk also works good with long running transaction ,keep these consideration while working with BizTalk .

     


    If this answers your question please mark it accordingly. If this post is helpful, please vote as helpful by clicking the upward arrow mark next to my reply

    Wednesday, February 22, 2017 11:56 PM
  • Thanks all
    Thursday, February 23, 2017 4:00 AM
  • That is very good question that is responsibility of IT integration architects but usually is on BizTalk developers plate.

    In short, you can use .NET and simulate basic required BizTalk behavior. Such developer will create some new framework on .NET to handle required functionality. Some PRO .NET developers used AppFabric to get rid of BizTalk.

    Then new requirements will come into the play like to connect to MS Dynamics, EDI or HL7.

    In the end CIOs are starting to think that maybe it was a good idea to use BizTalk from start.

    So .NET Framework here is like shelf products and equipment in Hope Depot store, and BizTalk is a PRO Rental section there with used heavy duty professional equipment.

    Thursday, February 23, 2017 3:27 PM
  • That really depends on what you want to achieve - is it just exchanging xml messages for a single app? You are better off sticking to the vanilla .NET app.

    But, if your requirements are that of enterprise integration - guaranteed delivery, only-once delivery, retries on failure and so on, you will end up writing a LOT of .NET code to achieve that. Add in the ability to communicate with different systems like SAP, mainframes, queuing systems (generally any system you can think of), an enterprise integration product like BizTalk is much the wiser choice.

    Also BizTalk ships a great deal of tooling that handles XML really well, which is not available generally with just the .NET framework - for example, the schema editor/designer.


    Thanks Arindam

    Thursday, February 23, 2017 3:45 PM
    Moderator
  • I was asked by .net guy in my team when we were doing the xml batch processes and calling third party's wcf services.
    Thursday, February 23, 2017 5:07 PM
  • If that is the ONLY requirement, you can go either way. But, if you think that there can be different types of integration requirements down the road - of different complexities, etc., you would be better served by an enterprise integration product like BizTalk Server. Also there would be lot more code/work needed in a .NET app for visibility, manageability of the overall process.

    Thanks Arindam

    Friday, February 24, 2017 8:23 AM
    Moderator