Apache Flink vs Spring Cloud Data Flow comparison

"Another feature is how Flink handles its radiuses. It has something called the checkpointing concept. You're dealing with billions and billions of requests, so your system is going to fail in large storage systems. Flink handles this by using the concept of checkpointing and savepointing, where they write the aggregated state into some separate storage. So in case of failure, you can basically recall from that state and come back."

"The end-to-end latency was drastically reduced, and our capability of handling high throughput has increased by using Flink."

"The top feature of Apache Flink is its low latency for fast, real-time data. Another great feature is the real-time indicators and alerts which make a big difference when it comes to data processing and analysis."

"The main advantage is the turnaround time, which has been reduced drastically because of Apache Flink, and now everything is in almost real time with no waiting or lag of data in the application while machine resources are utilized much more efficiently."

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

"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."

"Apache Flink provides faster and low-cost investment for me; I find it to have low hardware requirements, and it's faster with low code, meaning it's easy to understand for moving the streaming data."

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

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

"The product is very user-friendly."

"There are a lot of options in Spring Cloud. It's flexible in terms of how we can use it. It's a full infrastructure."

"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."

"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."

"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."

"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."

"In terms of improvement, there should be better reporting. You can integrate with reporting solutions but Flink doesn't offer it themselves."

"The machine learning library is not very flexible."

"In a future release, they could improve on making the error descriptions more clear."

"The solution could be more user-friendly."

"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 should provide more examples and sample code related to streaming to help me better adapt and utilize the tool."

"In terms of improvement, there should be better reporting. You can integrate with reporting solutions but Flink doesn't offer it themselves."

"The documentation on offer is not that good."

"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."

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

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

"The visual user interface could use some help; it needs improvement."

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

"Spring Cloud Data Flow could improve the user interface. We can drag and drop in the application for the configuration and settings, and deploy it right from the UI, without having to run a CI/CD pipeline. However, that does not work with Kubernetes, it only works when we are working with jars as the Spring Cloud Data Flow applications."

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

"It's an open source."

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

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

"It's an open-source solution."

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

"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."