Geeks With Blogs

News View Michael Stephenson's profile on BizTalk Blog Doc View Michael Stephenson's profile on LinkedIn
Michael Stephenson keeping your feet on premise while your heads in the cloud


5 minutes on the lips a lifetime on the hips 


I wish I had a pound for every time a work around is implemented in a BizTalk solution to make up for some issue with an application your trying to integrate with. This is often referred to as technical or architectural debt. One of the good things about BizTalk is that as an integration platform it has a number of way that this "dirty" side to integration can still be managed effectively but one of the problems customers often have is the long term implications of this debt. BizTalk often becomes an easy place to implement integration workarounds rather than deal with the core issue.


With this anti pattern I have related it to a common phrase in the world of diet and health. The phrase relates well to this anti-pattern because you may get a project where a workaround (which in a lot of cases should be referred to as a "hack") is implemented to deal with an immediate project issue and it can often be a very quick thing. People often don't think of this as cutting corners but often it is and the implications of this short term workaround is that you inherit additional maintenance overhead for a very long time afterwards.


In my experience I think that less than 25% of the times a project implements a workaround does this technical debt ever get repaid properly and with a lot of projects an organization isn't even able to track the level of technical debt it has.



  • Poor architectural decision making processes
  • Isolated project decisions with no governance
  • In experienced BizTalk team
  • Lack of communication about issues and problem solving approaches
  • Lack of measurement of technical debt



  • Future projects inherit the pain from technical debt
  • Workarounds built on top of workarounds
  • Projects tend to get messy



It's a difficult thing to cure because its really about an organisations culture and how they do projects. Having a strong architectural governance process can help a lot and having good escalation process can help too. I would recommend you should do the following:


  • Log all workarounds that get implemented somewhere
  • Measure the size of the workaround
  • Measure the predicted long term impact of the workaround
  • Review these regularly


One of the things I have done in the past is to use the BizTalk Solution Analyser tool to help me understand how changes in a source code structure have been implemented as a way to try to help me identify workarounds which may have been implemented by a project.



 This anti-pattern is by no means specific to BizTalk but I see it a lot in the BizTalk world and I wondered what other peoples thoughts about this or any examples people can share.

Posted on Thursday, July 26, 2012 5:52 PM BizTalk , Patterns and Anti Patterns | Back to top

Comments on this post: BizTalk Anti Pattern – 5 minutes on the lips a lifetime on the hips

# re: BizTalk Anti Pattern – 5 minutes on the lips a lifetime on the hips
Requesting Gravatar...
If you are searching any calendar then you click our website.In this site we create a attractive calendar this will be very useful for you.
july 2017 Calendar Printable
July 2017 calendar printable
July calendar 2017 printable
2017 July calendar
calendar 2017 July
calendar for July 2017
Left by sudhasharma on Jun 03, 2017 3:07 AM

Your comment:
 (will show your gravatar)

Copyright © Michael Stephenson | Powered by: