Aiven Platform vs Google Cloud Dataflow comparison

"One of the most valuable features of Aiven Platform is that it handles the upgrades for us seamlessly, saving us time that would be spent on routine upgrades."

"What I like best about the tool is that the process for the services is faster compared to other methods. It's easier to use because Aiven for Apache Kafka handles the maintenance, so we have less to manage. We only use Kafka to manage its connectivity."

"The best feature of Google Cloud Dataflow is its practical connectedness."

"The solution allows us to program in any language we desire."

"The product's installation process is easy...The tool's maintenance part is somewhat easy."

"Google Cloud Dataflow has made it very easy for detailed monitoring and logging features for pipeline performance assessment."

"It is a scalable solution."

"The most valuable features of Google Cloud Dataflow are the integration, it's very simple if you have the complete stack, which we are using, it is overall very easy to use, user-friendly, and cost-effective if you know how to use it, and the solution is very flexible for programmers, if you know how to do scripts or program in Python or any other language, it's extremely easy to use."

"Migrating our batch processing jobs to Google Cloud Dataflow led to a reduction in cost by 70%."

"The integration within Google Cloud Platform is very good."

"I would really like to see Aiven Platform add a user interface for database backups, as this would eliminate the need for a third-party solution."

"One challenge we face is when we want to update the version, for example, from 3.6 to 3.7. It will spawn new nodes, and then there's rebalancing and syncing from other brokers. There's high CPU usage during this process, so the solution can't be used for a while, causing some downtime in our services. To tackle this challenge, we schedule maintenance updates during low-traffic periods when there's less risk and fewer users use the services."

"Occasionally, dealing with a huge volume of data causes failure due to array size."

"Currently, not all error logs are available to users and this could make debugging failed jobs very difficult."

"The technical support is very hard to reach."

"Google Cloud Dataflow should include a little cost optimization."

"I would like to see improvements in consistency and flexibility for schema design for NoSQL data stored in wide columns."

"The system could function in an automated fashion and provide suggestions based on past transactions to achieve better scalability."

"When I deploy the product in local errors, a lot of errors pop up which are not always caught. The solution's error logging is bad. It can take a lot of time to debug the errors. It needs to have better logs."

"Google Cloud Data Flow can improve by having full simple integration with Kafka topics. It's not that complicated, but it could improve a bit. The UI is easy to use but the experience could be better. There are other tools available that do a better job."

"On a scale from one to ten, where one is cheap, and ten is expensive, I rate the solution's pricing a seven to eight out of ten."

"The solution is not very expensive."

"The price of the solution depends on many factors, such as how they pay for tools in the company and its size."

"The solution is cost-effective."

"The tool is cheap."

"On a scale from one to ten, where one is cheap, and ten is expensive, I rate Google Cloud Dataflow's pricing a four out of ten."

"Google Cloud is slightly cheaper than AWS."

"Google Cloud Dataflow is a cheap solution."