We performed a comparison between Amazon SQS and PubSub+ Event Broker based on real PeerSpot user reviews.
Find out in this report how the two Message Queue (MQ) Software solutions compare in terms of features, pricing, service and support, easy of deployment, and ROI."I appreciate that Amazon SQS is fully integrated with Amazon and can be accessed through normal functions or serverless functions, making it very user-friendly. Additionally, the features are comparable to those of other solutions."
"SQS is very stable, and it has lots of features."
"With SQS, we can trigger events in various cloud environments. It offers numerous benefits for us."
"One of the useful features is the ability to schedule a call after a certain number of messages accumulate in the container. For example, if there are ten messages in the container, you can perform a specific action."
"We use the tool in interface integrations."
"It is stable and scalable."
"The libraries that connect and manage the queues are rich in features."
"The most valuable feature of Amazon SQS is the interface."
"When it comes to granularity, you can literally do anything regarding how the filtering works."
"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."
"We like the seamless flexibility in protocol exchange offering without writing a code."
"The event portal and the diversity of deployment options in a hybrid landscape are the most valuable features."
"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."
"Guaranteed Messaging allows for us to transport messages between on-prem and the cloud without any loss of data."
"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."
"Sometimes, we have to switch to another component similar to SQS because the patching tool for SQS is relatively slow for us."
"It would be easier to have a dashboard that allows us to see everything and manage everything since we have so many queues."
"The initial setup of Amazon SQS is in the middle range of difficulty. You need to learn Amazon AWS and know how to navigate, create resources, and structures, and provide rules."
"As a company that uses IBM solutions, it's difficult to compare Amazon SQS to other solutions. We have been using IBM solutions for a long time and they are very mature in integration and queuing. In my role as an integration manager, I can say that Amazon SQS is designed primarily for use within the Amazon ecosystem and does not have the same level of functionality as IBM MQ or other similar products. It has limited connectivity options and does not easily integrate with legacy systems."
"Sending or receiving messages takes some time, and it could be quicker."
"Support could be improved."
"I cannot send a message to multiple people simultaneously. It can only be sent to one recipient."
"The solution is not available on-premises so that rules out any customers looking for the messaging solution on-premises."
"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 product should allow third-party agents to be installed. Currently, it is quite proprietary."
"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."
"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 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."
"We've pointed out some things with the DMR piece, the event mesh, in edge cases where we could see a problem. Something like 99 percent of users wouldn't ever see this problem, but it has to do with if you get multiple bad clients sending data over a WAN, for example. That could then impact other clients."
"If you create one event in the past, you cannot resend it."
"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."
Amazon SQS is ranked 4th in Message Queue (MQ) Software with 13 reviews while PubSub+ Event Broker is ranked 6th in Message Queue (MQ) Software with 15 reviews. Amazon SQS is rated 8.2, while PubSub+ Event Broker is rated 8.6. The top reviewer of Amazon SQS writes "Stable, useful interface, and scales well". 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 SQS is most compared with Apache Kafka, Redis, Amazon MQ, Anypoint MQ and VMware RabbitMQ, whereas PubSub+ Event Broker is most compared with Apache Kafka, IBM MQ, ActiveMQ, VMware RabbitMQ and Amazon SNS. See our Amazon SQS vs. PubSub+ Event Broker report.
See our list of best Message Queue (MQ) Software vendors.
We monitor all Message Queue (MQ) Software 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.
