We performed a comparison between Amazon Kinesis and PubSub+ Event Broker based on real PeerSpot user reviews.
Find out in this report how the two Streaming Analytics solutions compare in terms of features, pricing, service and support, easy of deployment, and ROI."What turns out to be most valuable is its integration with Lambda functions because you can process the data as it comes in. As soon as data comes, you'll fire a Lambda function to process a trench of data."
"I have worked in companies that build tools in-house. They face scaling challenges."
"Its scalability is very high. There is no maintenance and there is no throughput latency. I think data scalability is high, too. You can ingest gigabytes of data within seconds or milliseconds."
"Setting Amazon Kinesis up is quick and easy; it only takes a few minutes to configure the necessary settings and start using it."
"Amazon Kinesis also provides us with plenty of flexibility."
"The most valuable feature is that it has a pretty robust way of capturing things."
"Amazon Kinesis's main purpose is to provide near real-time data streaming at a consistent 2Mbps rate, which is really impressive."
"The integration capabilities of the product are good."
"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."
"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 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 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 like the seamless flexibility in protocol exchange offering without writing a code."
"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."
"When it comes to granularity, you can literally do anything regarding how the filtering works."
"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."
"It would be beneficial if Amazon Kinesis provided document based support on the internet to be able to read the data from the Kinesis site."
"For me, especially with video streams, there's sometimes a kind of delay when the data has to be pumped to other services. This delay could be improved in Kinesis, or especially the Kinesis Video Streams, which is being used for different use cases for Amazon Connect. With that improvement, a lot of other use cases of Amazon Connect integrating with third-party analytic tools would be easier."
"Something else to mention is that we use Kinesis with Lambda a lot and the fact that you can only connect one Stream to one Lambda, I find is a limiting factor. I would definitely recommend to remove that constraint."
"I think the default settings are far too low."
"One thing that would be nice would be a policy for increasing the number of Kinesis streams because that's the one thing that's constant. You can change it in real time, but somebody has to change it, or you have to set some kind of meter. So, auto-scaling of adding and removing streams would be nice."
"Amazon Kinesis should improve its limits."
"If there were better documentation on optimal sharding strategies then it would be helpful."
"Snapshot from the the from the the stream of the data analytic I have already on the cloud, do a snapshot to not to make great or to get the data out size of the web service. But to stop the process and restart a few weeks later when I have more data or more available of the client teams."
"I would like them to design topic and queue schemas, mapping them to the enterprise data structure."
"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 deployment process is complex."
"If you create one event in the past, you cannot resend it."
"The product should allow third-party agents to be installed. Currently, it is quite proprietary."
"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."
"The integrations could improve in PubSub+ Event Broker."
"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."
Amazon Kinesis is ranked 1st in Streaming Analytics with 24 reviews while PubSub+ Event Broker is ranked 10th in Streaming Analytics with 15 reviews. Amazon Kinesis is rated 8.0, while PubSub+ Event Broker is rated 8.6. The top reviewer of Amazon Kinesis writes "Used for media streaming and live-streaming data". 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 Kinesis is most compared with Azure Stream Analytics, Amazon MSK, Confluent and Apache Flink, whereas PubSub+ Event Broker is most compared with Apache Kafka, IBM MQ, ActiveMQ, VMware RabbitMQ and Confluent. See our Amazon Kinesis vs. PubSub+ Event Broker report.
See our list of best Streaming Analytics vendors.
We monitor all Streaming Analytics 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.
