PubSub+ Platform is primarily used for guaranteed delivery of messages from across systems, for microservice-based development, and for high-speed data consumption purposes. Guaranteed transmission of messages is another key use case.

The unique functions I appreciate about PubSub+ Platform are that it allows me to design my solution in a graphical manner, which is not available in many other products, and the design can also be pushed to the actual infrastructure layer, making it quite advantageous.

Mesh technology is useful in scenarios where different geographies have to be connected, although such situations are not commonly found. It is beneficial but not a super-used feature of PubSub+ Platform.

The event replay function is quite mature in PubSub+ Platform, allowing me to replay messages that are days in the past, which is a good feature.

The main benefits PubSub+ Platform provides for the end-user include building a robust and scalable system with very low network latency, which improves the customer experience, whether using mobile phones or applications. This type of messaging framework is extremely important, and Solace is a very good product in that space. Nowadays, most applications are built using microservices technology, with small microservices interchanging messages via PubSub+ Platform. Without it, realizing a scalable system would not be possible; for example, one cannot have Netflix or similar services that require quick data transit and a good user experience, ensuring that data cannot be lost in transit.

The analytics part of PubSub+ Platform is quite useful as it can connect with many analytical software tools, mainly for analysis of system logs, such as Splunk, DataDog, or Prometheus. It has the flexibility to connect with any of these and supports OpenTelemetry, which is not available in many other products, making traceability very easy. I can see how a message travels from a source system to the target system, end-to-end, along with what happens to that message along the path, making the analytics quite good.

Potential areas for improvement in PubSub+ Platform are its authentication mechanisms, which could be slightly better. While simple authentication using basic methods is easy, moving to more robust mechanisms like certificates or OAuth requires a bit deeper technical expertise.

I feel there is a lack of functionality in PubSub+ Platform; Solace has introduced microservices and micro-integrations recently with some capabilities, but they can improve on these. They also have some AI agent capabilities that are quite unknown, so if they can disclose this information properly, perhaps through blogs or detailed descriptions, it could be better.

I have been working with PubSub+ Platform for about five years.

I would rate the stability of PubSub+ Platform as a nine.

In terms of scalability, I would rate PubSub+ Platform as quite scalable, around 9.99.

I rate Solace's technical support as good; they can come on calls and assist quite well, so I could give them an eight.

The initial setup for PubSub+ Platform is not that difficult; it depends on the environment where I want to use it. If I use it on the cloud, it is quite straightforward, but in a Kubernetes environment, it needs a little bit of support.

Pricing-wise for PubSub+ Platform, I find it a little expensive, so I would rate it at six.

The main competitors in the market for PubSub+ Platform are IBM MQ and Kafka, with Kafka being the primary competitor.

If I compare the three solutions, I believe PubSub+ Platform provides a clear advantage for me because I can design my solution easily, which helps in building on an interface level.

Regarding security and compliance features, I have not explored that area much; it is not a compliance-oriented product, so I do not see any relevance of compliance concerning GDPR or similar regulations. I would rate this review an 8.5 overall.

I describe the main use cases for PubSub+ Platform as wanting to use it as a messaging queue pipeline for managing the data stream events in our IoT platform while I was working at an IoT-based company.

The best features of PubSub+ Platform include being highly scalable, allowing us to handle billions and billions of events. Configuring and managing PubSub+ Platform is straightforward and simple while being highly reliable.

The use of PubSub+ Platform has positively impacted my organization because we are using GCP for our systems, so we did not have to go outside of GCP's ecosystem.

Additional in-line information about certain things on PubSub+ Platform could be more beneficial for new users who are just starting to use this technology.

The analytics tools integrated within PubSub+ Platform are good, as it has already integrated with cloud logging and the cloud logging features, making the analytics pretty good already.

I think the stability of PubSub+ Platform is pretty good, and I would rate it at eight.

For my use case, I would rate the scalability of PubSub+ Platform 10 out of 10, but since I have not worked on a huge scale, I cannot comment on that.

I have looked into PubSub+ Platform's support forums to read and understand a few things that I did not understand. If you are talking about Google's team support, I have less idea about it.

In my opinion, the setup of PubSub+ Platform is straightforward.

I do not know about the pricing of PubSub+ Platform because I did not manage the instance.

I have utilized PubSub+ Platform's event replay feature when we were debugging issues, and it definitely helps me understand how or where things broke, quickly enabling us to upgrade the codebase and add additional fixes.

I think the documentation for PubSub+ Platform is pretty good and neat, so I would rate it an eight. I would rate this review an overall eight.

My typical use case for the PubSub+ Platform is as an event-driven solution for communication between two components.

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.

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.

I have more than 4 years of experience working with the PubSub+ Platform solution.

We don't know which deployment model we are using.

The PubSub+ Platform is a stable solution.

The scalability of the platform can be rated 8 out of 10.

We are not administrators, so we never reached out to support for the PubSub+ Platform.

The initial setup of the solution is an administrator setup, and we just use it. For us, using it is straightforward.

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.

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.

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.

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.

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.

We have been working with Solace for about three to four years.

Stability is generally good, but occasionally we encounter delivery failures. These issues are usually traced back to specific nodes not working correctly.

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.

I do not directly interact with customer support, but from what I hear from the admin team, they are responsive and resolve issues quickly.

We have also tried Rabbit MQ. However, the user community for Kafka is larger, offering more discussions and solutions in public forums.

We evaluated Rabbit MQ and Kafka before deciding to use PubSub+.

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.

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.

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.

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.

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.

I've used the solution for two years.

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.

We implemented the solution with the help of our own in-house team.

PubSub+ Event Broker is used to help manage architectures, such as real-time integrations of business processes and systems.

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.

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.

I have used PubSub+ Event Broker within the past 12 months.

The solution is stable. We are informed about any outage that happens.

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.

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.

We had a range of technical people involved in deploying this solution with a maximum of 10 assisting in the process.

The price of the solution is expensive.

I rate PubSub+ Event Broker a nine out of ten.

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.

The event portal and the diversity of deployment options in a hybrid landscape are the most valuable features.

The licensing and the cost are the major pitfalls.

I have been using the solution for almost two years.

It is a very scalable and robust solution. I rate it a ten out of ten.