TrustRadius: an HG Insights company

Save this comparison

Save this comparison

Add Product

Recommended Comparisons

    Overview
    ProductRatingMost Used ByProduct SummaryStarting Price

    Amazon Kinesis

    Score10 out of 10
    N/AAmazon Kinesis is a streaming analytics suite for data intake from video or other disparate sources and applying analytics for machine learning (ML) and business intelligence.

    $0.01

    per GB data ingested / consumed

    RabbitMQ

    Score9.6 out of 10
    N/ARabbitMQ, an open source message broker, is part of Pivotal Software, a VMware company acquired in 2019, and supports message queue, multiple messaging protocols, and more. RabbitMQ is available open source, however VMware also offers a range of commercial services for RabbitMQ; these are available as part of the Pivotal App Suite.N/A
    Pricing
    Amazon KinesisRabbitMQ
    Editions & Modules
    Amazon Kinesis Video Streams
    $0.00850
    per GB data ingested / consumed
    Amazon Kinesis Data Streams
    $0.04
    per hour per stream
    Amazon Kinesis Data Analytics
    $0.11
    per hour
    Amazon Kinesis Data Firehose
    tiered pricing starting at $0.029
    per month first 500 TB ingested
    No answers on this topic
    Offerings
    Pricing Offerings
    Amazon KinesisRabbitMQ
    Free Trial
    NoNo
    Free/Freemium Version
    NoNo
    Premium Consulting/Integration Services
    NoNo
    Entry-level Setup FeeNo setup feeNo setup fee
    Additional Details——
    More Pricing Information
    Community Pulse
    Amazon KinesisRabbitMQ
    Considered Both Products
    Amazon AWS
    No answer on this topic
    Open Source
    No answer on this topic
    Key User Insights
    Would buy again
    No answers on this topic
    91%
    Would buy again
    10 Answers
    Delivers good value for the price
    No answers on this topic
    100%
    Delivers good value for the price
    11 Answers
    Happy with the feature set
    No answers on this topic
    91%
    Happy with the feature set
    10 Answers
    Lived up to sales and marketing promises
    No answers on this topic
    100%
    Lived up to sales and marketing promises
    7 Answers
    Implementation went as expected
    No answers on this topic
    100%
    Implementation went as expected
    11 Answers
    Features
    Amazon KinesisRabbitMQ
    Streaming Analytics
    Comparison of Streaming Analytics features of Amazon Kinesis and RabbitMQ
    Feature
    Amazon Kinesis
    8.3
    2 Ratings
    6% above category average
    RabbitMQ
    -
    Ratings
    Real-Time Data Analysis10.01 Ratings00 Ratings
    Data Ingestion from Multiple Data Sources9.02 Ratings00 Ratings
    Low Latency9.02 Ratings00 Ratings
    Integrated Development Tools9.02 Ratings00 Ratings
    Data wrangling and preparation10.01 Ratings00 Ratings
    Linear Scale-Out6.12 Ratings00 Ratings
    Data Enrichment5.01 Ratings00 Ratings
    Best Alternatives
    Amazon KinesisRabbitMQ
    Small Businesses
    Google Cloud Dataflow
    Score9.1 out of 10
    No answers on this topic
    Medium-sized Companies
    No answers on this topic
    Apache Kafka
    Score8.9 out of 10
    Enterprises
    TIBCO Streaming
    Score5 out of 10
    Apache Kafka
    Score8.9 out of 10
    All AlternativesView all alternativesView all alternatives
    User Ratings
    Amazon KinesisRabbitMQ
    Likelihood to Recommend
    9.0
    (3 ratings)
    9.9
    (11 ratings)
    Usability
    -
    (0 ratings)
    8.0
    (1 ratings)
    Support Rating
    7.1
    (2 ratings)
    6.5
    (4 ratings)
    User Testimonials
    Amazon KinesisRabbitMQ
    Likelihood to Recommend
    Amazon AWS
    Amazon Kinesis is a great replacement for Kafka and it works better whenever the components of the solution are AWS based. Best if extended fan-out is not required, but still price-performance ratio is very good for simplifying maintenance.
    I would go with a different option if the systems to be connected are legacy, for instance in the case of traditional messaging clients.
    Incentivized
    Read full review
    Open Source
    It is highly recommended that if you have microservices architecture and if you want to solve 2 phase commit issue, you should use RabbitMQ for communication between microservices. It is a quick and reliable mode of communication between microservices. It is also helpful if you want to implement a job and worker mechanism. You can push the jobs into RabbitMQ and that will be sent to the consumer. It is highly reliable so you won't miss any jobs and you can also implement a retry of jobs with the dead letter queue feature. It will be also helpful in time-consuming API. You can put time-consuming items into a queue so they will be processed later and your API will be quick.
    Incentivized
    Read full review
    Pros
    Amazon AWS
    • Processing huge loads of data
    • Integrating well with IoT Platform on Amazon
    • Integration with overall AWS Ecosystem
    • Scalability
    Incentivized
    Read full review
    Open Source
    • What RabbitMQ does well is what it's advertised to do. It is good at providing lots of high volume, high availability queue. We've seen it handle upwards of 10 million messages in its queues, spread out over 200 queues before its publish/consume rates dipped. So yeah, it can definitely handle a lot of messages and a lot of queues. Depending on the size of the machine RabbitMQ is running on, I'm sure it can handle more.
    • Decent number of plugins! Want a plugin that gives you an interface to view all the queues and see their publish/consume rates? Yes, there's one for that. Want a plugin to "shovel" messages from one queue to another in an emergency? Check. Want a plugin that does extra logging for all the messages received? Got you covered!
    • Lots of configuration possibilities. We've tuned over 100 settings over the past year to get the performance and reliability just right. This could be a downside though--it's pretty confusing and some settings were hard to understand.
    Incentivized
    Read full review
    Cons
    Amazon AWS
    • Not a queue system, so little visibility into "backlog" if there is any
    • Confusing terminology to make sure events aren't missed
    • Sometimes didn't seem to trigger Lambda functions, or dropped events when a lot came in
    Incentivized
    Read full review
    Open Source
    • It breaks communication if we don't acknowledge early. In some cases our work items are time consuming that will take a time and in that scenario we are getting errors that RabbitMQ broke the channel. It will be good if RabbitMQ provides two acknowledgements, one is for that it has been received at client side and second ack is client is completed the processing part.
    Incentivized
    Read full review
    Usability
    Amazon AWS
    No answers on this topic
    Open Source
    RabbitMQ is very easy to configure for all supported languages (Python, Java, etc.). I have personally used it on Raspberry Pi devices via a Flask Python API as well as in Java applications. I was able to learn it quickly and now have full mastery of it. I highly recommend it for any IoT project.
    Incentivized
    Read full review
    Support Rating
    Amazon AWS
    The documentation was confusing and lacked examples. The streams suddenly stopped working with no explanation and there was no information in the logs. All these were more difficult when dealing with enhanced fan-out. In fact, we were about to abort the usage of Kinesis due to a misunderstanding with enhanced fan-out.
    Incentivized
    Read full review
    Open Source
    I gave it a 10 but we do not have a support contract with any company for RabbitMQ so there is no official support in that regard. However, there is a community and questions asked on StackOverflow or any other major question and answer site will usually get a response.
    Incentivized
    Read full review
    Alternatives Considered
    Amazon AWS
    The main benefit was around set up - incredibly easy to just start using Kinesis. Kinesis is a real-time data processing platform, while Kafka is more of a message queue system. If you only need a message queue from a limited source, Kafka may do the job. More complex use cases, with low latency, higher volume of data, real time decisions and integration with multiple sources and destination at a decent price, Kinesis is better.
    Incentivized
    Read full review
    Open Source
    RabbitMQ has a few advantages over Azure Service Bus 1) RMQ handles substantially larger files - ASB tops out at 100MB, we use RabbitMQfor files over 200MB 2) RabbitMQ can be easily setup on prem - Azure Service Bus is cloud only 3) RabbitMQ exchanges are easier to configure over ASB subscriptions ASB has a few advantages too 1) Cloud based - just a few mouse clicks and you're up and running
    Incentivized
    Read full review
    Return on Investment
    Amazon AWS
    • Caused us to need to re-engineer some basic re-try logic
    • Caused us to drop some content without knowing it
    • Made monitoring much more difficult
    • We eventually switched back to SQS because Kinesis is not the same as a Queue system
    Incentivized
    Read full review
    Open Source
    • Positive: we don't need to keep way too many backend machines around to deal with bursts because RabbitMQ can absorb and buffer bursts long enough to let an understaffed set of backend services to catch up on processing. Hard to put a number to it but we probably save $5k a month having fewer machines around.
    • Negative: we've got many angry customers due to queues suddenly disappearing and dropping our messages when we try to publish to them afterward. Ideally, RabbitMQ should warn the user when queues expire due to inactivity but it doesn't, and due to our own bugs we've lost a lot of customer data as a result.
    • Positive: makes decoupling the web and API services from the deeper backend services easier by providing queues as an interface. This allowed us to split up our teams and have them develop independently of each other, speeding up software development.
    Incentivized
    Read full review
    ScreenShots