Likelihood to Recommend 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.
Read full review If you want to stream high volumes of data, be it for ETL streaming or event sourcing, Google Cloud Pub/Sub is your go-to tool. It's easy to learn, easy to observe its metrics and scales with ease without additional configuration so if you have more producers of consumers, all you need to do is to deploy on k8s your solutions so that you can perform autoscaling on your pods to adjust to the data volume. The DLQ is also very transparent and easy to configure. Your code will have no logic whatsoever regarding orchestrating pubsub, you just plug and play. However, if you are not in the Google Cloud Pub/Sub environment, you might have trouble or be most likely unable to use it since I think it's a product of Google Cloud.
Read full review Pros Processing huge loads of data Integrating well with IoT Platform on Amazon Integration with overall AWS Ecosystem Scalability Read full review With a pub/sub architecture the consumer is decoupled in time from the publisher i.e. if the consumer goes down, it can replay any events that occurred during its downtime. It also allows consumer to throttle and batch incoming data providing much needed flexibility while working with multiple types of data sources A simple and easy to use UI on cloud console for setup and debugging It enables event-driven architectures and asynchronous parallel processing, while improving performance, reliability and scalability Read full review Cons 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 Read full review Would be nice if the queue could be extended beyond 7 days. We found it a bit tricky replay unacknowledged messages when needed. Read full review Likelihood to Renew It serves all of our purposes in the most transparent way I can imagine, after seeing other message queueing providers, I can only attest to its quality.
Read full review Usability It has many libraries in many languages, google provides either good guides or they're AI generated code libraries that are easy to understand. It has very good observability too.
Read full review Reliability and Availability I have never faced a single problem in 4 years.
Read full review Performance It's very fast, can be even better if you use protobuf.
Read full review Support Rating 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.
Read full review They have decent documentation, but you need to pay for support. We weren't able to answer all our questions with the documentation and didn't have time to setup support before we needed it so I can't give it a higher rating but I think it tends to be a bit slow unless you're a GCP enterprise support customer.
Read full review Alternatives Considered 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.
Read full review Having used Amazon Web Services SNS & SQS I can say that even if the latter may offer more features, Google Cloud Pub/Sub is easier to use. On the other hand, usage of SNS & SQS as well as documentation and troubleshooting is easier with the AWS solution. Since we are not using GCP only for Pub/Sub the choice depends on other variables.
Read full review Scalability You can just plug in consumers at will and it will respond, there's no need for further configuration or introducing new concepts. You have a queue, if it's slow, you plug in more consumers to process more messages: simple as that.
Read full review Return on Investment 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 Read full review Increased Efficiency with reliable and Google managed services up all the time wit Disaster Recovery in place as well Definitely Lower costs being a cloud based solution and easier to setup Faster Project delivery and go to market plan for the business use cases basis this technology at the back end Read full review ScreenShots