AWS Auto Scaling vs. InterSystems Ensemble

There are two elements to auto-scaling. The first, adding/removing servers when [the] load varies, is the easy part. This is what AWS Auto Scaling does. The second is orchestration. This making sure your read replica doesn't receive requests until it is operational or making sure that your new [webserver] has finished starting JBoss, updating its sources, and loading your application before it is registered with the load balancer[.]

Incentivized

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

• Smart scaling decisions
• Automatically maintain performance
• Pay per use

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

• Auto scaling features are very easy to use it.
• can decrease numbers steps to configure the auto scaling functionality
• New GUI screen need to improve for auto scaling functionality

• 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.

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.

The hardware provided is decent and customizable. They have lots of different options for everything[.]

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

• Pay per use, great ROI.
• Saves cost across departments.
• Workload and pc.

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