Apache Flink vs Spring Cloud Data Flow comparison

"We are very happy with the product, and we have been able to achieve all of the use cases that we are expected to deliver for our customers."

"Allows us to process batch data, stream to real-time and build pipelines."

"This is truly a real-time solution."

"The ease of usage, even for complex tasks, stands out."

"Apache Flink is meant for low latency applications. You take one event opposite if you want to maintain a certain state. When another event comes and you want to associate those events together, in-memory state management was a key feature for us."

"Flink moved on to becoming a standard technology for location platform."

"Apache Flink's best feature is its data streaming tool."

"The product helps us to create both simple and complex data processing tasks. Over time, it has facilitated integration and navigation across multiple data sources tailored to each client's needs. We use Apache Flink to control our clients' installations."

"This product will assist us in saving costs in many ways: No longer need to continue paying high fees for proprietary software, reduce the number of software engineers needed to support the product, and achieve faster time to market by using this product for our middleware."

"The most valuable features of Spring Cloud Data Flow are the simple programming model, integration, dependency Injection, and ability to do any injection. Additionally, auto-configuration is another important feature because we don't have to configure the database and or set up the boilerplate in the database in every project. The composability is good, we can create small workloads and compose them in any way we like."

"The dashboards in Spring Cloud Dataflow are quite valuable."

"The solution's most valuable feature is that it allows us to use different batch data sources, retrieve the data, and then do the data processing, after which we can convert and store it in the target."

"Overall, Spring Cloud Data Flow is a really good solution and a lot cheaper than a lot of infrastructure provided by big companies like Google or Amazon."

"The most valuable feature is real-time streaming."

"The ease of deployment on Kubernetes, the seamless integration for orchestration of various pipelines, and the visual dashboard that simplifies operations even for non-specialists such as quality analysts."

"The best thing I like about Spring Cloud Data Flow is its plug-and-play model."

"The TimeWindow feature is a bit tricky. The timing of the content and the windowing is a bit changed in 1.11. They have introduced watermarks. A watermark is basically associating every data with a timestamp. The timestamp could be anything, and we can provide the timestamp. So, whenever I receive a tweet, I can actually assign a timestamp, like what time did I get that tweet. The watermark helps us to uniquely identify the data. Watermarks are tricky if you use multiple events in the pipeline. For example, you have three resources from different locations, and you want to combine all those inputs and also perform some kind of logic. When you have more than one input screen and you want to collect all the information together, you have to apply TimeWindow all. That means that all the events from the upstream or from the up sources should be in that TimeWindow, and they were coming back. Internally, it is a batch of events that may be getting collected every five minutes or whatever timing is given. Sometimes, the use case for TimeWindow is a bit tricky. It depends on the application as well as on how people have given this TimeWindow. This kind of documentation is not updated. Even the test case documentation is a bit wrong. It doesn't work. Flink has updated the version of Apache Flink, but they have not updated the testing documentation. Therefore, I have to manually understand it. We have also been exploring failure handling. I was looking into changelogs for which they have posted the future plans and what are they going to deliver. We have two concerns regarding this, which have been noted down. I hope in the future that they will provide this functionality. Integration of Apache Flink with other metric services or failure handling data tools needs some kind of update or its in-depth knowledge is required in the documentation. We have a use case where we want to actually analyze or get analytics about how much data we process and how many failures we have. For that, we need to use Tomcat, which is an analytics tool for implementing counters. We can manage reports in the analyzer. This kind of integration is pretty much straightforward. They say that people must be well familiar with all the things before using this type of integration. They have given this complete file, which you can update, but it took some time. There is a learning curve with it, which consumed a lot of time. It is evolving to a newer version, but the documentation is not demonstrating that update. The documentation is not well incorporated. Hopefully, these things will get resolved now that they are implementing it. Failure is another area where it is a bit rigid or not that flexible. We never use this for scaling because complexity is very high in case of a failure. Processing and providing the scaled data back to Apache Flink is a bit challenging. They have this concept of offsetting, which could be simplified."

"Apache Flink should improve its data capability and data migration."

"In terms of stability with Flink, it is something that you have to deal with every time. Stability is the number one problem that we have seen with Flink, and it really depends on the kind of problem that you're trying to solve."

"There are more libraries that are missing and also maybe more capabilities for machine learning."

"Apache Flink is very powerful, but it can be challenging for beginners because it requires prior experience with similar tools and technologies, such as Kafka and batch processing."

"One way to improve Flink would be to enhance integration between different ecosystems. For example, there could be more integration with other big data vendors and platforms similar in scope to how Apache Flink works with Cloudera. Apache Flink is a part of the same ecosystem as Cloudera, and for batch processing it's actually very useful but for real-time processing there could be more development with regards to the big data capabilities amongst the various ecosystems out there."

"The state maintains checkpoints and they use RocksDB or S3. They are good but sometimes the performance is affected when you use RocksDB for checkpointing."

"Failure is another area where it is a bit rigid or not that flexible."

"The documentation on offer is not that good."

"On the tool's online discussion forums, you may get stuck with an issue, making it an area where improvements are required."

"I would improve the dashboard features as they are not very user-friendly."

"The solution's community support could be improved."

"The configurations could be better. Some configurations are a little bit time-consuming in terms of trying to understand using the Spring Cloud documentation."

"There were instances of deployment pipelines getting stuck, and the dashboard not always accurately showing the application status, requiring manual intervention such as rerunning applications or refreshing the dashboard."

"Some of the features, like the monitoring tools, are not very mature and are still evolving."

"Spring Cloud Data Flow is not an easy-to-use tool, so improvements are required."

"Apache Flink is open source so we pay no licensing for the use of the software."

"It's an open source."

"The solution is open-source, which is free."

"This is an open-source platform that can be used free of charge."

"It's an open-source solution."

"If you want support from Spring Cloud Data Flow there is a fee. The Spring Framework is open-source and this is a free solution."

"The solution provides value for money, and we are currently using its community edition."

"This is an open-source product that can be used free of charge."