Try our new research platform with insights from 80,000+ expert users

AWS Auto Scaling vs Avada Software Infrared360 comparison

 

Comparison Buyer's Guide

Executive SummaryUpdated on Jul 24, 2024

Review summaries and opinions

We asked business professionals to review the solutions they use. Here are some excerpts of what they said:
 

Categories and Ranking

Avada Software Infrared360
Ranking in Application Performance Monitoring (APM) and Observability
77th
Average Rating
8.8
Number of Reviews
13
Ranking in other categories
Business Activity Monitoring (5th), Message Oriented Middleware (MOM) (11th), Server Monitoring (36th)
AWS Auto Scaling
Ranking in Application Performance Monitoring (APM) and Observability
15th
Average Rating
8.8
Reviews Sentiment
7.0
Number of Reviews
21
Ranking in other categories
No ranking in other categories
 

Mindshare comparison

As of April 2025, in the Application Performance Monitoring (APM) and Observability category, the mindshare of Avada Software Infrared360 is 0.1%, up from 0.1% compared to the previous year. The mindshare of AWS Auto Scaling is 0.1%, up from 0.1% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Application Performance Monitoring (APM) and Observability
 

Featured Reviews

it_user685326 - PeerSpot reviewer
An offsite team performs a daily infrastructure health check and sends reports to the technical/management teams.
Administration, Monitoring, and Delegation are the most valuable features of the solution. * Administration: It provides a centralized audit trail of all the infrastructure changes. * Monitoring: It gives the ability to integrate with my company's global notification system, and the ability to proactively automate corrective actions. * Delegation: It allows non-technical users to inspect their individual components within the total infrastructure without disturbing other components and without bothering the technical teams.
Mbula Mboma - PeerSpot reviewer
Boosts deployment efficiency with seamless automatic scaling capabilities
My primary use case for Auto Scaling is mainly to deploy applications at scale Auto Scaling has made the deployment of applications more efficient, allowing us to manage traffic and maintain performance as user counts increase. Auto Scaling is a cool feature that works well and its automatic…

Quotes from Members

We asked business professionals to review the solutions they use. Here are some excerpts of what they said:
 

Pros

"The administration piece makes it very easy to do MQ administration. It gives us a lot more flexibility and capabilities."
"It's what we use for monitoring our MQ system, so the features that they provide are just really, really good."
"It allows non-technical users to inspect their individual components within the total infrastructure without disturbing other components and without bothering the technical teams."
"It has role-based access to queues, giving us more insights into problems."
"Monitoring that ties into our incident management system"
"We have easily created use case testing harnesses for specific flows that incorporate various message types."
"It can scale."
"The various scaling options available, such as step scaling, are particularly useful."
"AWS Auto Scaling is very good for managing traffic and creating new instances when necessary."
"I would highly recommend Auto Scaling to others because it is a fantastic feature that simplifies scaling processes and makes deployment efficient."
"The tool gives you the flexibility to scale up and grow. The solution is also fast to deploy."
"The setup is not very complex."
"Auto Scaling is a cool feature that works well and its automatic scaling capabilities are very useful."
"The solution's monitoring effectively monitors our application and CPU utilization."
 

Cons

"Some of the graphics in the interface could be improved. It's pretty basic. Some interfaces are not up to what you're used to seeing on other, more Windows-like tools."
"The user interface could be sexier and more ergonomic. The competing products have similar problems."
"We are still working with the FTE/MFT subscription monitoring and reporting functionality. That is an area in which we would like to see further development taking place."
"We desire a dashboard that could accumulate BOQ lengths per tenant on one screen for all tenants."
"The UI can be cumbersome - but we are still using the Viper interface and we have not had the time to check out the Alloy interface which is supposed to be much improved."
"One area where they could improve is with their documentation. Some sections are not up to date with new release information and providing additional samples in some areas would be very helpful."
"Flexibility in configuring the workload is missing in AWS Auto Scaling."
"The solution is not out-of-the-box and you have to study to use it. It should be more easier to use."
"The only area of improvement is the speed at which servers are launched. When cleaning up to six servers at a time, it can take up to 15 to 20 minutes to launch new servers."
"The solution must improve automation."
"It requires a downtime before deploying the Auto Scaling group."
"The tool must include AI features."
"AWS Auto Scaling's documentation could be better."
"There hasn't been a need for improvements."
 

Pricing and Cost Advice

"Start small, then increase licensing later as per your demand."
"Because the licensing is at the QMGR level, you need to have at least a small cushion of licenses for occasional enterprise needs."
"Avada Software's licensing metric is very good because the license fees are based on the number of connections (which have not increased for us very much over the years) rather than the CPU processing power (which increases significantly whenever our hardware is upgraded) or the number of users (which has increased for us a lot since our original purchase)."
"Our internal budget calculation model incorporates the pricing per endpoint for any new projects. However, as our footprint for distributed queue managers shrinks as part of our shared middleware hub deployment, the initial licensing and support costs have been reduced over the last five years."
"The product has moderate pricing."
"The pricing is good. I have not had any customers that have complained about the price."
"AWS Auto Scaling is a cheap solution."
"AWS Auto Scaling's price is high."
"AWS Auto Scaling is a pay-per-use and pay-as-you-use service."
"AWS Auto Scaling is an expensive solution."
"The product is expensive."
report
Use our free recommendation engine to learn which Application Performance Monitoring (APM) and Observability solutions are best for your needs.
848,253 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
41%
Manufacturing Company
9%
Computer Software Company
7%
Hospitality Company
5%
No data available
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
 

Questions from the Community

Ask a question
Earn 20 points
What do you like most about AWS Auto Scaling?
The tool's most valuable feature is vertical auto-scaling, which is easy to use. However, most companies now prefer horizontal scaling. I set up the health check integration to monitor CPU usage. W...
What is your experience regarding pricing and costs for AWS Auto Scaling?
The pricing of Auto Scaling is medium range, neither high nor low.
What needs improvement with AWS Auto Scaling?
It is sometimes very critical to deploy on AWS since some servers are already running in the background. There are challenges for employees on how to deploy at a given time. It requires a downtime ...
 

Also Known As

Infrared360
AWS Auto-Scaling
 

Overview

 

Sample Customers

USBank, Southwest Airlines, Visiting Nurse Services of New York, Aon Hewitt, Parker Hannifin,  Cantonal Bank of Zurich (ZKB), Hagemeyer NA, and many others
Expedia, Intuit, Royal Dutch Shell, Brooks Brothers
Find out what your peers are saying about AWS Auto Scaling vs. Avada Software Infrared360 and other solutions. Updated: April 2025.
848,253 professionals have used our research since 2012.