Tuesday, June 5, 2012

More BizTalk Anti-Patterns

Just assuming is also a BizTalk Anti-Pattern

About a month ago I accepted a contract as a BizTalk Developer for a major care product service provider. The project was to incorporate United Parcel Services mapping and routing services into existing BizTalk 2009 Applications. This was a major project with a fairly large budget. They were willing to pay a fairly high rate.

Part of the scope of the project was to incorporate the Windows Azure Service Bus.

Unfortunately I did not ask any questions about their current environment.  I just assumed….

  • It wasn’t until I started that I found out they were using BizTalk 2009 Standard.

  • They were not using Maps, WCF-Lob Adapters, Pipeline Components, or the ESB Toolkit. The only had a few schemas

  • They did everything in .Net code and WCF Services and called these services from Expression Shapes in Orchestrations

I was told that the were only using BizTalk for Guaranteed Delivery.

I demonstrated how they could easily develop this application in BizTalk without the need to write a lot of code.


They had no interest in changing their use of BizTalk. Nor were they interested in upgrading to Enterprise.



  1. So did you stay and do it their way, or move on? That's the tough decision as a consultant who is must pay his bills.

    1. I terminated my contract. With qualified BizTalk people in high demand, finding a new contract was fairly easy.

  2. What was your reason behind you thought BizTalk 2009 Standard was a bad practice for them?

    1. This was supposed to be a mission critical application for them. They had planned to integrate with Azure AppFabric. The application needed to support thousands of mobile clients throughout the world

      There current system did not support high-availability or automatic disaster recovery. The proper way to do this is to cluster the SQL servers.

      BizTalk Standard is for customers that do not require high-availability and redundancy.

  3. Interesting. So doesnt BT Standard support any high availability?

  4. And with standard you can have a max of only 2 processors. not good for large implementations.

  5. The Standard Edition allows:

    Single server solution/single message box
    Remote or local DB