AWS Auto Scaling vs. InterSystems Ensemble (legacy product)

1. When down time needs to be eliminated. 2. Have templates that can be used for future application deployments. 3. Templates can serve as a documentation for keep track of server configuration. 4. Handling of high usage periods like reporting season.

Incentivized

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

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

We use AWS auto scaling for scaling up our cloud virtual machines to handle the increase or decrease in workload. It really helps us to satisfy the demand because it doesn't take lot of time to spin up new machines. I gave the rating 10 because it really does help you to handle the sudden spike in number of requests.

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.

AWS auto scaling handles the sudden surge in demand very effectively and it is also very cost effective in terms of pricing compared to the other service providers I have used. That is the main reason I opted for AWS auto scaling and also it is very reliable and has less fault tolerance.

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.

• Better fault tolerance.
• Almost availability of our services
• Reduced cost

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.