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."Messages easily flow from publisher or application to subscriber."
"It's a simple communication service that allows us to communicate with customers."
"We have found the key feature of this solution to be the simplicity of sending out notifications."
"Amazon SNS has SMS notifications as well. Most of the other solutions have only email notifications."
"The integration between the features is excellent."
"The initial setup of Amazon SNS was easy."
"The most valuable feature of Amazon SNS is speed. It's really fast."
"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 most valuable feature of PubSub+ Event Broker is the scaling integration. Prior to using the solution, it was done manually with a file, and it can be done instantly live."
"As of now, the most valuable aspects are the topic-based subscription and the fanout exchange that we are using."
"Going from something where we had outages and capacity issues constantly to a system that was able to scale with the massive market data and messaging spikes that happened during the initial stages of the COVID crisis in March, we were able to scale with 40 plus percent growth in our platform over the course of days."
"In my assessment of Solace against other products — as I was responsible for evaluating various products and bringing the right tool into companies in the past — I worked with multiple platforms like RabbitMQ, Confluent, Kafka, and various other tools in the market. But I found the event mesh capability to be a very interesting as well as fulfilling capability, towards what we want to achieve from a digital-integration-strategy point of view... It's distributed, yet it is intelligently connected. It can also span and I can plug and play any number of brokers into the event mesh, so it's a great deal. That's a differentiator."
"We like the seamless flexibility in protocol exchange offering without writing a code."
"Guaranteed Messaging allows for us to transport messages between on-prem and the cloud without any loss of data."
"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 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."
"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 terms of improvement, I would like to have better customer support for SNS. We can then manage it very easily."
"I expect Amazon SNS to provide some capabilities to allow the configuration process to be done in a single script."
"We would like the integration with third party applications to be improved within this solution."
"Messages should flow through a gateway without the need for a mediator."
"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."
"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."
"The product should allow third-party agents to be installed. Currently, it is quite proprietary."
"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."
"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."
"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."
"The section on observability pertains to understanding the functioning of an event crash. Instead of focusing on how the crash occurs, attention is given to the observable aspects, such as a memory pipeline where one person pushes messages and another reads them. However, this pipeline often encounters issues, such as the reader being unavailable, causing the system to become stuck and preventing the messages from moving forward. This can lead to the pipeline being permanently stalled."
"It could be cheaper. It could also have easier usage. It is a brilliant product, but it is quite complex to use."
"The integrations could improve in PubSub+ Event Broker."
"If you create one event in the past, you cannot resend it."
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, ActiveMQ, VMware Tanzu Data Services and TIBCO Rendezvous. 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.