InterSystems Ensemble (legacy product) vs. Mule ESB

If you want to connect different environments, laboratories, companies, etc. Each one uses its own system and services to transmit information. Instead of having to make costly developments for each of the companies to connect, with a single common process many companies could be integrated in very short times. It offers a wide range of common architectures and methods that reduce development time by almost 75%. You do not need to add databases, complex automation connection systems, etc., ... everything is in the same application.

Incentivized

Well Suited for:

• REST APIs.
• Rapid API Development.
• Most suitable for integration with SFDC.
• Batch processing.
• Parallel processing.

Less appropriate for:

• Integration with Database.
• Exposing SOAP services.
• Small organizations, because it is super costly.

Incentivized

• Easy to use: The simplicity of its programming language allows fast learning. Visual environment to generate complex code.
• Robust: A fall of the system will not be a problem. Never again will information of the transactions in progress be lost. Never more messages lost.
• Connect to the world: The most popular connection is possible to implement quickly. FTP, File folder, TCP, SMPT, REST.... all method are ready to use. Only define "where" and "how"

Incentivized

• As an ESB it provides great flexibility to add/remove systems in the integration easily. Highly scalable.
• Supports any kind of system to be integrated, Supports Java.
• Lightweight.

Incentivized

• Given that Ensemble and Cache are one of if not the only true fully object orientated database/development technologies for massive transactional data systems its customizability is extensive and it just comes down to the creativity of the developer to get the products to pretty much do whatever they want to do with it. However, this is not necessarily obvious to newcomers to the technology.
• The developer community could do with greater participation from the software developers/application specialists and engineers within InterSystems.
• More extensive documentation and greater access to proven working solutions particularly in the realm of some of the lesser known or new and upcoming technologies.

• Logging the Database query in production with out changing the log4j level

Incentivized

I have yet to raise an issue with InterSystems WRC that they have been unable to resolve to my satisfaction in the 20+ years that I have worked with their products.

There is just no comparison. Try it and see for yourself. Furthermore based on information from software houses I have interacted with over the years it far out paces products like WebSphere.

Hands down, Mule is more cost-effective than Informatica, either on-prem or cloud, and the value only goes up form there. Reusability and ease of creation makes in-house training simple and the end result is we leverage Mule for much more than what we initially considered it for. Having used Oracle and TIBCO before as well, I find they are the tools of yesterday, not able to keep up in terms of functionality or price. Jitterbit would be a more relevant comparison, but Mule won out in the bake-off we did between them.

Incentivized

• I was able to develop a fully functional integration engine linking pharmacy systems with pharmacy robotics in less than three months in comparison with the year that the previous software development company had taken to develop a solution that was incomplete and did not work using Microsoft technology.
• The engine I developed was so stable and adaptable that it quickly replaced the equivalent engine supplied by the robot manufacturers own software development team.
• It has proven to be so effective that it is now the product of choice for future developments within the organization replacing Microsoft technologies which were the previous company standard.

• Created a means to have a synergy with developers - quickly made us productive
• Ease of integration with Mule connectors - quicker releases
• Initial configuration was a challenge. Would have been more challenging without Mule Support

Incentivized