No more typing reviews! Try our Samantha, our new voice AI agent.

Amazon SNS vs Avada Software Infrared360 comparison

Why PeerSpot?
 

Comparison Buyer's Guide

Executive Summary

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

Amazon SNS
Ranking in Message Oriented Middleware (MOM)
6th
Average Rating
9.0
Reviews Sentiment
7.9
Number of Reviews
12
Ranking in other categories
No ranking in other categories
Avada Software Infrared360
Ranking in Message Oriented Middleware (MOM)
12th
Average Rating
8.8
Number of Reviews
13
Ranking in other categories
Application Performance Monitoring (APM) and Observability (71st), Business Activity Monitoring (6th), Server Monitoring (34th)
 

Mindshare comparison

As of September 2026, in the Message Oriented Middleware (MOM) category, the mindshare of Amazon SNS is 5.3%, down from 5.4% compared to the previous year. The mindshare of Avada Software Infrared360 is 4.9%, up from 2.9% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Message Oriented Middleware (MOM) Mindshare Distribution
ProductMindshare (%)
Amazon SNS5.3%
Avada Software Infrared3604.9%
Other89.8%
Message Oriented Middleware (MOM)
 

Featured Reviews

HarshalJethwa - PeerSpot reviewer
Cloud Operations Engineer at a tech vendor with 51-200 employees
Event-driven messaging has improved real-time notifications and incident response
In my experience, the best features Amazon SNS offers include the ability to create an event-driven architecture and services, as well as real-time notifications.When I mention real-time capabilities and integration with other AWS services, specific integrations or real-time features that stand out most to me are S3 bucket events including creating a bucket, creating an object, updating an object, modifying an object, and deleting an object. Additionally, with CloudWatch alarms, when I get an alarm on CloudWatch, it will notify me via email using Amazon SNS. The same applies to application events. Amazon SNS has impacted my organization positively because using it, we are able to create an event-driven architecture and send notifications for events or incidents. Amazon SNS has helped my team respond faster, improved reliability, and saved time. Specifically, because of it, we are able to identify events as soon as possible. It saves our time and we can also process them as soon as possible.
WK
ICT Architect at a tech services company with 51-200 employees
Role-based access to queues, giving us more insights into problems
* We now have the possibility of getting a central perspective on all tenants. * We have defined access roles for developers. Therefore, they can 'read in' their queues on the development and testing stages. With special roles, they may also write. This improves our development and testing cycle. * For operative systems, we have restricted the access. Still, selected people can react if something is happening in the various BOQs.

Quotes from Members

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

Pros

"The best aspect of this solution is its simplicity. We just have to create topics and can have as many subscriptions as we want under any topic we create."
"We see ROI because we use the features that help us and make our product work better."
"The most valuable feature of Amazon SNS is speed. It's really fast."
"Overall, I am very happy with this service."
"The mobile push notifications are the most valuable. Previously, we used to use Firebase Cloud Messaging (FCM) for this functionality. It is a Google service for sending push notifications. Android did not have a good service for sending push notifications, but now, Amazon SNS integrates with FCM. Under the road, it is actually using FCM, but we can see all the metrics on our AW service itself, which makes it a lot easier instead of using a third-party service for this particular functionality."
"Push notifications are the most valuable. I have mostly used push notifications for my system. Amazon SNS supports all devices for push notification services. It supports iOS, Android, and Windows notifications. It provides reliable push notification services. We have queues, and we can track which notifications have failed or had some issues. We can then figure out the issue. We can also debug the issue because of which our push notification didn't reach the end users."
"The initial setup of Amazon SNS was easy."
"Messages easily flow from publisher or application to subscriber."
"One way it's helped the business is how you're able to empower MQ users, without your administrators, to be able to do different types of processes in the environment."
"The administration piece makes it very easy to do MQ administration. It gives us a lot more flexibility and capabilities."
"Administration, Monitoring, and Delegation are the most valuable features of the solution."
"It has role-based access to queues, giving us more insights into problems."
"It allows non-technical users to inspect their individual components within the total infrastructure without disturbing other components and without bothering the technical teams."
"The ability for development teams to have access to their MQ queues has freed us up as administrators to do things other than chase down an application’s message for research purposes."
"IR360 does not require a large team to manage our entire middleware estate and allows the leveraging of a logical model of reuse."
"We have easily created use case testing harnesses for specific flows that incorporate various message types."
 

Cons

"There needs to be more documentation on the integration with different platforms."
"Messages should flow through a gateway without the need for a mediator."
"A major issue with AWS as a whole is that it has a lot of services that do the same thing, and people get confused about which one to use in which scenario."
"A major issue with AWS as a whole is that it has a lot of services that do the same thing, and people get confused about which one to use in which scenario. Previously, we used to use SNS for connecting microservices. SNS has around six types of subscribers. We can subscribe to Lambda, HTTP, HTTPS, SMS, email, and push notifications. We used to use HTTP endpoints and Lambda for connecting to microservice systems. Now we have something called EventBridge, which actually does that for you. For connecting to services, we should just use EventBridge rather than SQS, SNS. I hear a lot of complaints from people wherein they do not understand when to use EventBridge and when to use SQS, SNS. They can remove these features so that it doesn't confuse users about when to use SQS, SNS, or EventBridge."
"In future releases, I want to see if the platforms that SMS can reach. It would be a good way to improve it. More platforms to be able to use it."
"The tool needs to have direct integration with AvPro."
"We would like the integration with third party applications to be improved within this solution."
"There could be more integration with other solutions."
"We desire a dashboard that could accumulate BOQ lengths per tenant on one screen for all tenants."
"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."
"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."
"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."
"We definitely need a better overview in terms of a dashboard giving us insights."
 

Pricing and Cost Advice

"It is the cheapest solution in the market. It is on a monthly basis. After a month, you are build based on your usage. There are no additional costs to the standard licensing fees."
"Amazon SNS is cheap and I would rate it a three out of ten. The pricing is usage-based."
"The solution has no up-front costs because you pay based on the number of messages you publish."
"One can use the tool for free."
"Their pricing is competitive. I would rate the cost four out of five."
"The pricing of push notifications and everything is quite fair. If you are using FCM under the hood, it is completely free. When you are using push notification on SMS, it is just a nominal price that you need to pay. SMS services are a lot more costly. It is because we don't have proper providers in India. That's why it gets a lot more costly in terms of SMS. This is the reason why we don't use SMS services from SNS itself. We use other third-party services like SMS Horizon. We use a third-party service for email services. It is almost free. It is just around $1 a month. Configuring Lambda is also quite cheap. You only pay for the Lambda usage. You don't pay for SNS itself."
"The pricing is very cheap."
"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)."
"Because the licensing is at the QMGR level, you need to have at least a small cushion of licenses for occasional enterprise needs."
"Start small, then increase licensing later as per your demand."
"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."
report
Use our free recommendation engine to learn which Message Oriented Middleware (MOM) solutions are best for your needs.
912,930 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Outsourcing Company
15%
Manufacturing Company
15%
Comms Service Provider
8%
Financial Services Firm
8%
Financial Services Firm
17%
Construction Company
15%
Comms Service Provider
7%
Outsourcing Company
6%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
By reviewers
Company SizeCount
Small Business8
Midsize Enterprise1
Large Enterprise4
By reviewers
Company SizeCount
Small Business4
Midsize Enterprise5
Large Enterprise5
 

Questions from the Community

What needs improvement with Amazon SNS?
I believe Amazon SNS could be improved because when you integrate it, you also need SQS, so it is a two-service job. It does not provide filtering or advanced routing, there is no ordering guarante...
What is your primary use case for Amazon SNS?
My main use case for Amazon SNS is that we use it for a messaging service with a publish-subscribe model to send messages to multiple subscribers.A specific example of how I use Amazon SNS for the ...
What advice do you have for others considering Amazon SNS?
The features I find valuable in Amazon SNS are messaging, real-time notifications, and the ability to create an event-driven architecture. I give this product a rating of 8 out of 10.
Ask a question
Earn 20 points
 

Also Known As

No data available
Infrared360
 

Overview

 

Sample Customers

PlayOn! Sports, NASA, Change Healthcare, FCBarcelona
USBank, Southwest Airlines, Visiting Nurse Services of New York, Aon Hewitt, Parker Hannifin,  Cantonal Bank of Zurich (ZKB), Hagemeyer NA, and many others
Find out what your peers are saying about Amazon SNS vs. Avada Software Infrared360 and other solutions. Updated: September 2026.
912,930 professionals have used our research since 2012.