F5 Distributed Cloud App Connect vs. InterSystems Ensemble

I thought F5 Distributed Cloud App Connect worked great to bridge the gap between our gcp environment and on prem. We were lacking in cloud funtionality for native load balancers but XC really connected the dots. We would most likely need a hybrid environment until the irules functionality improves for a few of our apps but most could be migrated over the XC.

Incentivized

• Best suited for fast development with a fundamental emphasis on object orientation
• Prohibitive costs for very small integration projects

• scheduled rollout
• distributed workforce

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

• ease of usage
• UI

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.

From what we have been able to test load/responsiveness is quick and when we've tested out reporting and troubleshooting modules they have pulled the correct information in quick timeframes. We haven't been able to test out any software integration with Splunk of other software on our system since we are still in early POC stages but from what we've been told we should be able to implement that in our environment

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.

ease of deployment

Incentivized

Mirth is another integration platform that we have used but its development, in Java, made us always create new methods every time a new product was integrated. Every connection process had to be developed from the beginning and it was not easy to reuse code. Nor did it allow us to have an extensive catalog of HL7 messaging, having to perform the validation of each and every one of its fields manually.

Incentivized

• Definitely reducing time to deploy
• Reducing time to patch/upgrade

Incentivized

• We have integrated 5 laboratories in a treatment monitoring system in less than a month of development. Being able to integrate the following in a period no longer than a week.

Incentivized