If I were to advise someone, I would ask the user what endpoints they want to touch. If I want to read something from Kafka and I want to put this thing on the S3 bucket, what is the alternative I have? 

I have Kafka Connect, where I can connect Kafka with one Kafka, and I can put it into an S3 bucket. Is this scalable? No. Is this monitoring No. 

We can't monitor it. We can't scale it. It's going to be a complete black box. The person who knows Kafka Connect, or Kafka, can understand what is happening there while using Kafka Connect. But if I compare it, I literally don't need to understand what Kafka is.

I know, "Okay, this is Kafka. These are the endpoints, and this is the URL I have to point to." That's it. My job is done. I will create a complete flow pipeline within, let's say, thirty minutes or something without having any current knowledge. I can read, I can Google it, and I can just implement it.

For people who are new to big data technologies like Kafka and BigQuery, I would give this solution an eight out of ten. 

Let's say you need to build a solution to read from Kafka and write to an S3 bucket. You could use Kafka Connect, but if your requirements change and you need to start reading from a database instead, Kafka Connect will not work. With Apache NiFi, you can easily modify your flow pipeline to start reading from the database instead.

If the volume is manageable, I would recommend it. Overall, I would rate the solution a six out of ten. 

I rate the solution an eight out of ten.

You have to independently develop a use case for using NiFi, then test it and do the integration to have a stable workflow. After this, you jump in and integrate with Kafka distributed messaging and also connecting to your MDM database.

I would rate Apache NiFi an eight out of ten.

The solution must be improved to compete with Kafka. As it is an open-source tool, it will take time to get all the functions. I would recommend the product to others. Overall, I rate the product a seven out of ten.

Phenomenal product. It is in its early stages, and through further development this product has the potential to be a powerhouse in the Big Data sector of the tech industry.

The architect needs to evaluate the entire architecture with this platform so eventually, we are left with our architects and we need to get approval from them to do that.

I would rate this solution an eight out of ten.

Think about your data flows as the directed graphs between low-level processing modules, so you can re-use as much of the path as possible for different data streams. Don’t create entirely separate flows for new data sources, i.e., if you can avoid it.

I would rate this solution an eight out of ten.

There are some claims that NiFi is cloud-native but we have tested it, and it's not.

I would rate this solution a seven out of ten.