• For shops that have no .net development expertise (or desire to do so) its a good tool. Also very good for shops that have lots of varying but lightweight integration tasks to do on a regular basis.

    Having said that, for those that have a few specific and consistent integration jobs that are a regular part of the production environment I would always use a purpose built solution in .NET (or C++ if you need that level of performance). In my experience the result is more efficient and reliable solution because you can add robust error detection and recovery procedures that make these jobs bulletproof. Does require competent .net software developer(s) though.

    The probability of survival is inversely proportional to the angle of arrival.