We performed a comparison between Amazon SNS and PubSub+ Event Broker based on real PeerSpot user reviews.
Find out in this report how the two Message Oriented Middleware (MOM) solutions compare in terms of features, pricing, service and support, easy of deployment, and ROI."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."
"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."
"Messages easily flow from publisher or application to subscriber."
"We have found the key feature of this solution to be the simplicity of sending out notifications."
"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."
"It's a simple communication service that allows us to communicate with customers."
"The integration between the features is excellent."
"The most valuable feature of Amazon SNS is speed. It's really fast."
"The most useful features has been the WAN optimization and probably the HybridEdge, which requires some third-party adapters or plugins. The idea that we can position Solace as a protocol-agnostic message transport fabric is key to our company having all manners of asynchronous messaging protocols from MQ, Kafka, JMS, etc. I really like the WAN optimization: Send once over a WAN, then distribute locally as many times as there are subscribers."
"This solution reduces the latency to access changes in real-time and the effort required to onboard a new subscriber. It also reduces the maintenance of each of those interfaces because now the publisher and subscribers are decoupled. Event Broker handles all the communication and engagement. We can just push one update, then we don't have to know who is consuming it and what's happening to that publication downstream. It's all done by the broker, which is a huge benefit of using Event Broker."
"The valuable feature of PubSub+ Event Broker is the speed of processing, publishing, and consumption."
"The event portal and the diversity of deployment options in a hybrid landscape are the most valuable features."
"One of the main reasons for using PubSub+ is that it is a proper event manager that can handle events in a reactive way."
"The way we can replicate information and send it to several subscribers is most valuable. It can be used for any kind of business where you've got multiple users who need information. Any company, such as LinkedIn, with a huge number of subscribers and any business, such as publishing, supermarket, airline, or shipping can use it."
"When it comes to granularity, you can literally do anything regarding how the filtering works."
"The topic hierarchy is pretty flexible. Once you have the subject defined just about anybody who knows Java can come onboard. The APIs are all there."
"We would like the integration with third party applications to be improved within this solution."
"We would like to have the option when someone leaves the organization or moves to another team, to remove notifications. Currently this needs to be done manually by the company admin."
"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."
"There needs to be more documentation on the integration with different platforms."
"Messages should flow through a gateway without the need for a mediator."
"The tool needs to have direct integration with AvPro."
"I recently worked with Firebase, and it provides an option to create a marketing campaign with a title and a specific image to inform our audience about something. We just design the campaign and then use the push notifications. It would be good if Amazon also adds a similar feature."
"There could be more integration with other solutions."
"Some of the feature's gaps with some of the open-source vendors have been closed in a lot of ways. Being more agile and addressing those earlier could be an area for improvement."
"If you create one event in the past, you cannot resend it."
"We have requested to be able to get into the payload to do dynamic topic hierarchy building. A current workaround is using the message's header, where the business data can be put into this header and be used for a dynamic topic lookup. I want to see this in action when there are a couple of hundred cases live. E.g., how does it perform? From an administration perspective, is the ease of use there?"
"The ease of management could be approved. The GUI is very good, but to configure and manage these devices programmatically in the software version is not easy. For example, if I would like to spin up a new software broker, then I could in theory use the API, but it would require a considerable amount of development effort to do so. There should be a tool, or something that Solace supports, that we could use for this, e.g., a platform like Terraform where we could use infrastructure as code to configure our source appliances."
"A challenge we currently have is Solace's ability to integrate with single sign-on in our Active Directory and other single sign-on tools and platforms that any company would have. It's important for the platforms to work. Typically, they support only LDAP-based connectivity to our SQL Servers."
"The licensing and the cost are the major pitfalls."
"One of the areas of improvement would be if we could tell the story a bit better about what an event mesh does or why an event mesh is foundational to a large enterprise that has a wide diversity of applications that are homegrown and a small number off the shelf."
"The deployment process is complex."
Amazon SNS is ranked 3rd in Message Oriented Middleware (MOM) with 11 reviews while PubSub+ Event Broker is ranked 2nd in Message Oriented Middleware (MOM) with 15 reviews. Amazon SNS is rated 9.0, while PubSub+ Event Broker is rated 8.6. The top reviewer of Amazon SNS writes "The best service available with easy message flow and a pay-as-you-go model". On the other hand, the top reviewer of PubSub+ Event Broker writes "Event life cycle management changes the way a designer or architect will design a topic and discover what is available". Amazon SNS is most compared with Amazon EventBridge, TIBCO Enterprise Message Service and IBM MQ, whereas PubSub+ Event Broker is most compared with Apache Kafka, IBM MQ, VMware RabbitMQ, ActiveMQ and Anypoint MQ. See our Amazon SNS vs. PubSub+ Event Broker report.
See our list of best Message Oriented Middleware (MOM) vendors.
We monitor all Message Oriented Middleware (MOM) reviews to prevent fraudulent reviews and keep review quality high. We do not post reviews by company employees or direct competitors. We validate each review for authenticity via cross-reference with LinkedIn, and personal follow-up with the reviewer when necessary.