"[...] Mule was designed around the philosophy of 'Adaptive Integration'. What this means for Mule users is that they can build best-of-bread integration solutions because they can choose which technologies to plug together with Mule. [...]"
About JBI he points the following assumptions and there consequences:
- XMLmessages will be used for moving data around
- Data Transformation is always XML-based
- Service contract will be WSDL
- No need for message streaming
- You need to implement a pretty heavy API to implement a service
- It’s not actually that clear what a service engine is in JBI
"[...] JBI seems to be a 'standard' written by middleware vendors for middleware vendors. This 'vendor view' of the world is one of the main reasons Open Source has done so well. Traditionally, Open Source has been written by developers much closer to the problem being tackled. These developers can deliver a better way of solving the problem using their domain knowledge, experience and the need for something better. This was the ultimate goal Mule and given the success of the project I believe that goal has been realized with the caveat that things can always be improved (which we continue to do). [...]"