Iguana versus Biztalk interface engines
Iguana was much simpler to install and configure than Biztalk. Iguana was much quicker and simpler to set up the first few examples. In Biztalk, the developer needs to switch back and forth between VS2012 Biztalk project and the Biztalk Server Administartion during development whereas Iguana uses one browser environment to accomplish both. Iguana uses lua scripting language for internal logic versus a Orchestration visual designer inside of VS2012. I found the lua script easier to use than the Orchestration visual designer.
The developer needs to understand quite a bit of the Biztalk architecture before getting started. Iguana on the other hand has a simpler model which can be grasped quickly. Biztalk and Iguana both can manage multiple machines from one console as needed for scalability.
I think that Biztalk would be a great fit for very large integration projects as it has an architecture designed for ultimate flexibility at the expense of added complexity. Many pre-built componenets are available for Biztalk and it is infinitely configurable. However each new task takes more effort due to this complexity. Iguana would be a better fit for other environments just due to it’s greater simplicty.
Interface Systems is a smaller company than Microsoft of course, but commands enough share of the interface market to stick around. It has 18.1% organization usage versus 9.7% for Biztalk in the HL7 interface world according to the 2014 HL7 Interface Technology Survey(http://corehealthtechnologies.com/main/wp-content/uploads/2014/10/2014-HL7-Interface-Technology-Survey-Results.pdf). Most companies in that survey planned to stay with their current interface provider(s).
I didn’t’ find any benchmarks. For what little it is worth, interfaceware (Iguana’s parent company) touted iguana’s speed and presented a client who switched from BizTalk to Iguana.
- Messages– Although not required, Bizttalk expects it’s messages to be converted to some xml schema for internal logic processing. Iguana passes the incomming message as string into the internal logic scripts which can parse, interrogate, transform as needed.
- Scripting languages– BizTalk has its own scripting language and can also extended modules and functions can be written C#. Iguana also has its own scripting language (Lua). I found Lua to be easy to learn and use.
- Processing Pipeline – BizTalk had a deep pre and post processing pipeline, which cuts both ways. Good is some cases, but added to the complexity in most cases. Iguana had a more straight-forward and simply pipeline model.
My experience with Iguana was more favorable. However, if you had a need for a more complex pre or post processing pipeline, BizTalk might be a better choice.