My typical use case for the PubSub+ Platform is as an event-driven solution for communication between two components.
PubSub+ Cloud Platform - Annual Commitment
Solace CorporationReviews from AWS customer
0 AWS reviews
-
5 star0
-
4 star0
-
3 star0
-
2 star0
-
1 star0
External reviews
9 reviews
from
and
External reviews are not included in the AWS star rating for the product.
Offers a seamless way to decouple applications, providing impressive performance and flexibility
What is our primary use case?
What is most valuable?
The best features of the tool include multiple impressive capabilities, such as the multi-level folder structure creation. Users can create a queue or topic in a folder structure under C with program files and software. The performance and scalability of the PubSub+ Platform are as impressive as Kafka.
The solution's ability to decouple message producers and consumers is exactly what we use these messaging solutions for, allowing us to have high cohesion and low coupling, making it an excellent solution for that purpose.
What needs improvement?
Regarding improving the PubSub+ Platform, I'm not sure about the pricing aspect, but I heard that it is quite expensive compared to Kafka. That's the only concern I can mention; otherwise, it was as impressive as Kafka, better than Kafka based on my experience working on the Solace and Kafka white paper.
For how long have I used the solution?
I have more than 4 years of experience working with the PubSub+ Platform solution.
What was my experience with deployment of the solution?
We don't know which deployment model we are using.
What do I think about the stability of the solution?
The PubSub+ Platform is a stable solution.
What do I think about the scalability of the solution?
The scalability of the platform can be rated 8 out of 10.
How are customer service and support?
We are not administrators, so we never reached out to support for the PubSub+ Platform.
How would you rate customer service and support?
Positive
How was the initial setup?
The initial setup of the solution is an administrator setup, and we just use it. For us, using it is straightforward.
What other advice do I have?
I have experience working with Kafka, PubSub+ Platform, and IBM MQ, all three of them.
We are customers, meaning my company uses Solace. We use it and customize it based on our needs.
Based on my experience, I would recommend other people use PubSub+ Platform.
Interested parties can contact me if they have any questions or comments about my review.
I rate the PubSub+ Platform a 9 out of 10.
Which deployment model are you using for this solution?
Answer omitted due to lack of information
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?
Other
Enhanced asynchronous processing with reliable message handling
What is our primary use case?
We use PubSub+ primarily for long processing messages. For instance, we generate customer forms, which take a longer time. We place these requests in queues, process them, and return them to the queues. This ensures that messages are not lost due to the time-consuming nature of such tasks. We also use PubSub+ for audit trails where we intercept requests, apply them, and store them in MongoDB, placing them in the queue before final processing.
How has it helped my organization?
PubSub+ has enhanced our asynchronous mode processing, ensuring that messages are not lost and requests are kept until fully processed. This means that messages do not get lost in the network or time out, thus improving reliability and efficiency.
What is most valuable?
Some valuable features include reconnecting topics, placing queues, and direct connections to MongoDB. The platform provides a dashboard to monitor the status of messages, such as how many have been processed or delivered, which is helpful for tracking performance.
What needs improvement?
The solution could be improved by enhancing the message pooling size for persistent messages to handle both small and large messages effectively. Additionally, providing a comprehensive dashboard to display metrics such as message throughput, connection rates, latency, and automated alerts would be highly beneficial.
For how long have I used the solution?
We have been working with Solace for about three to four years.
What do I think about the stability of the solution?
Stability is generally good, but occasionally we encounter delivery failures. These issues are usually traced back to specific nodes not working correctly.
What do I think about the scalability of the solution?
While I haven't directly explored horizontal or vertical scaling techniques, PubSub+ can process transactions efficiently and scale to handle multiple topics and queues. It supports enterprise-level features and multi-cloud messaging. Our use of internal cloud models assists in scalability, enabling multiple consumers and publishers to use the system simultaneously.
How are customer service and support?
I do not directly interact with customer support, but from what I hear from the admin team, they are responsive and resolve issues quickly.
How would you rate customer service and support?
Positive
Which solution did I use previously and why did I switch?
We have also tried Rabbit MQ. However, the user community for Kafka is larger, offering more discussions and solutions in public forums.
Which other solutions did I evaluate?
We evaluated Rabbit MQ and Kafka before deciding to use PubSub+.
What other advice do I have?
I recommend considering Solace due to its enterprise-level features, high throughput, cloud integration, and security. It is a top competitor among similar products and offers significant benefits in reliability and scalability.
Which deployment model are you using for this solution?
On-premises
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?
Other
Flexible and versatile with a simple portal
What is our primary use case?
We handle publishing/emitting events to the PubSub+ Broker via one protocol, and it seamlessly makes the event available for multiple consumers with different protocols without writing code is one of the primary use cases for us.
As an architect, I wanted to implement an event-driven architecture, majorly focusing on a cloud solution with a PubSub pattern.
Out of curiosity, our CoE team explored Solace PubSub+, and after several months of testing with our requirements, this was the kind of solution we needed.
How has it helped my organization?
Previously, we used on-prem Kafka for event distribution. The Kafka cluster was self-managed and hence required a dedicated team and infrastructure to manage. We wanted a cloud solution, and Kafka was already available as a SaaS offering, yet we wanted a better and more compatible solution with respect to protocols and security. Hence, we opted for PubSub+ with the support of AMQP, JMS, MQTT, and HTTPS. Without writing code, we were successful in creating event-driven microservices; parallelly, administering the cluster was not our responsibility anymore.
What is most valuable?
We like the seamless flexibility in protocol exchange offering without writing a code. This is probably the most useful feature of Solace apart from the structural Topic segments.
Solace PubSub+ has understood and implemented the best features of multiple PubSub brokers. I have seen segmenting of topics in IBM MQ PubSub and have used that feature a lot. With such versatility, Solace has implemented one the most demanding PubSub broker, hence a PubSub+. It is a simple portal for event-driven architecture driving the entire microservices framework.
What needs improvement?
Feature-wise, it has almost everything that I can ask from an architect's point of view.
For improvements, I would suggest increasing the max payload size to a limit of 100MB or more. The current max payload size is limited to 5MB.
"Events" are supposed to be small in size, yet, as the name suggests for "broker", a broker should be capable of handling large payloads as well. Even Confluent Kafka provides bigger payload size support for enterprise usage licenses.
For how long have I used the solution?
I've used the solution for two years.
Which solution did I use previously and why did I switch?
We have used IBM MQ pubsub and Kafka. We were moving away from the IBM stack and implementing microservices. Kafka would have been a good choice, yet keeping the future scope in mind; we opted for Solace.
What about the implementation team?
We implemented the solution with the help of our own in-house team.
Which deployment model are you using for this solution?
Private Cloud
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?
Google
Useful integration, reliable, and easy deployment
What is our primary use case?
PubSub+ Event Broker is used to help manage architectures, such as real-time integrations of business processes and systems.
What is most valuable?
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.
What needs 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.
More observing capabilities should be added.
For how long have I used the solution?
I have used PubSub+ Event Broker within the past 12 months.
What do I think about the stability of the solution?
The solution is stable. We are informed about any outage that happens.
What do I think about the scalability of the solution?
We have had times when messages were stuck and we have to flush the pipeline. There is a gap in the scalability.
We have two customers using this solution.
How was the initial setup?
The initial setup of PubSub+ Event Broker is easy. We can simply connect the solution to an SAP S4/HANA. We had no difficulties.
To install SAP in the public cloud, we need to provide SAP with a basic configuration file, which is a straightforward JSON file. SAP takes care of the entire installation process based on the configuration provided by PubSub+ Event Broker. Therefore, most of the installation work is handled by SAP, and we only need to specify our requirements and the duration of the process. It's a relatively straightforward process.
What about the implementation team?
We had a range of technical people involved in deploying this solution with a maximum of 10 assisting in the process.
What's my experience with pricing, setup cost, and licensing?
The price of the solution is expensive.
What other advice do I have?
I rate PubSub+ Event Broker a nine out of ten.
Which deployment model are you using for this solution?
Public Cloud
A scalable and stable solution with a user-friendly portal
What is our primary use case?
An enterprise-grade event broker for mediation of events produced by a heterogeneous hybrid landscape of SAP and non-SAP systems at scale.
An event registry/catalogue and a user-friendly visualization of event flow.
What is most valuable?
The event portal and the diversity of deployment options in a hybrid landscape are the most valuable features.
What needs improvement?
The licensing and the cost are the major pitfalls.
For how long have I used the solution?
I have been using the solution for almost two years.
What do I think about the scalability of the solution?
It is a very scalable and robust solution. I rate it a ten out of ten.
Pub Sub+ solace
What do you like best about the product?
Better filtering on the messages , easy
Understanding on the flow very transparent flow details, easy maintenance, eliminates complex code
Understanding on the flow very transparent flow details, easy maintenance, eliminates complex code
What do you dislike about the product?
Message size is 10mb max for one message this is a little drawback
What problems is the product solving and how is that benefiting you?
Solving the problem of using JMS triggers and filters to divide data as all can be done in sending data to different topics
Simply the best
What do you like best about the product?
The best part of the product is ease of setting up the platform. The available deployment options are quite straight forward and even more easy to set up. In term of the infrastructure needs, the whole platform can be set up with HA and with DR with just 6 servers. That’s something really amazing. Additionally, the dynamic routing capabilities and event mesh provided by the product allows extreme flexibility when it comes to routing events to interested consumers. The product supports a wide variety of protocol support which would enable almost every consumer to connect to the PubSub+ platform.Extreme performance is also a great plus.
What do you dislike about the product?
It would have been great if the product could access the event payload and perform routing based on that. Also, the constraint of triplet nodes as unit of scaling needs to be removed
What problems is the product solving and how is that benefiting you?
Solace PubSub+ is positioned as an enabler platform to support the organization's journey towards event-driven architecture. So far, the journey has been incredible with the successful rollout of pilot project leveraging the platform
Best Cloud based Messaging As a Service
What do you like best about the product?
Easy to setup and quick to deploy. Great documentation and user interfaces. Excellent customer services and support. Periodic communications related to upgrades, outages, issue addressing, technical blogs, use cases and other items related to the product.
What do you dislike about the product?
Nothing specific. Overall, a great experience.
What problems is the product solving and how is that benefiting you?
Considering the cost of hosting a middleware infrastructure in a DC, the cloud based Solace PubSub+ is a right product for target customers across Small and Medium Enterprises. With the extensive platform support and great documentation, this is ideal switch for any organization which uses a legacy messaging middleware platform with competitive pricing.
In case of specific business problems, Solace PubSub+ allows me to interact with other cloud based services with legacy applications by acting as a perfect middleware sitting in the cloud. If I have to integrate with Solace in campus with legacy, that is also possible without much code changes.
In case of specific business problems, Solace PubSub+ allows me to interact with other cloud based services with legacy applications by acting as a perfect middleware sitting in the cloud. If I have to integrate with Solace in campus with legacy, that is also possible without much code changes.
Recommendations to others considering the product:
Any organisation planning to reduce the cost of their campus or DC deployed middleware infrastructure should try this product in a pilot basis. It is available in all cloud services. Given the level of support is available 24*7 or 24*5, depending upon the subscription, it is an ideal choice. In addition, the global DR strategy helps in achieving compliance and Resilience to the applications of the organizations and their business.
Solace expierence
What do you like best about the product?
Working with Solace Vendor is awesome. their products are very good like pubsub, Solace PCF tile
What do you dislike about the product?
Their product has some limitation as they dont support more than 5 message-VPNs
What problems is the product solving and how is that benefiting you?
this is great product for messaging. it has benefit as they provide hybrid cloud deployments
showing 1 - 9