Spring Cloud Data Flow vs TIBCO BusinessWorks comparison

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

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

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

"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 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 most valuable feature is real-time streaming."

"The product is very user-friendly."

"The most valuable features are the stability and the time to market."

"The ability to link to different technologies is valuable to us."

"The solution is very scalable. It can handle a lot. We have encryption plus integration servers running on that platform currently."

"It is a very robust system."

"I like TIBCO BusinessWorks because it has a user-friendly GUI for developing solutions."

"One of the most valuable features is data transformation. We have some legacy systems which are in old technology, like SOAP, whereas the new ones are in REST. So we use BusinessWorks to transform data from one format to another, from SOAP to REST."

"The solution is stable. We haven't had any serious technical issues."

"The most important thing is that it is easy for developers to work with."

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

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

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

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

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

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

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

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

"Improve Business Studio's stability to further minimize development time."

"The communication protocols could be improved."

"Its price can be improved. For medium enterprises, it is a very expensive tool. In the market, you won't get many resources for this solution. You won't find many developers in the market very easily. The latest version of TIBCO (6.4 or 6.x) is not very stable. It has got many issues. We have raised this with TIBCO, and they are taking a lot of time to come up with a fix, which is making us move away from this product. Some of the performance-tuning aspects are also missing in version 6. They should provide performance-related fixes, which will be helpful for the customers. If you are migrating from the current version to the container-supported version, it is quite expensive. The product has evolved, but it is very pricey. That's one of the challenges. They have provided all the features that are there in other products, but this is a platform upgrade. The platform has completely been changed from 5.x to 6.x, and we can't use the same environment. We can't run both versions on the same server as VM. The development environment is entirely different. In version 5.x, there was a proprietary designer. Now, it has common plug-ins developed on top of Eclipse."

"The cost of this product is too expensive for smaller companies or those with a small number of integrations."

"The cost has room for improvement."

"There are multiple plugins which increase the number of product installations."

"The cost of the solution has room for improvement."

"They don't support out of the box - you have to buy adapters or you have to have the technology."

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

"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 payments made for service are the only addition to the standard licensing fees that we pay for the solution."

"The cost depends on the components required."

"The product is not cheap."

"The license is expensive, and I would rate it one out of ten."

"Licensing scheme is too rigid"

"I think BusinessWorks is more expensive compared to other products. We have the ELA, so at least we have some sort of bargain or discount with that. But for a start-up, it's very expensive compared to other ESBs."

"TIBCO BusinessWorks is a very expensive solution."

"My understanding is that the licensing is very costly."