Spring Cloud Data Flow vs webMethods.io comparison

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

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

"The product is very user-friendly."

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

"In the API gateway, there is a new feature that allows us to filter logs within a payload. This has been a useful feature."

"The solution has a very comprehensive and versatile set of connectors. I've been able to utilize it for multiple, different mechanisms. We do a lot of SaaS and we do have IoT devices and the solution is comprehensive in those areas."

"EDI is robust and integration with SAP is good."

"The core product can be used not only for automatic file transfers between applications, but also as an Enterprise Service Bus (ESB)."

"​Broker and UM are the best features."

"It’s fairly easy to view, move, and mange access across different components. Different component types are categorized and can be viewed in a web based administration console."

"It's obvious that the heart of the product lies here. It's comprised of all aspects of ESB (Enterprise Gateway, Adapter, TN, Java) and BPM (task, rules engine)."

"One of the most important features is that it gives you the possibility to do low-level integration. It provides a lot of features out of the box, and over the years, it has matured so much that any problem that is there in the market can be solved with this product. We can meet any requirements through customizations, transformations, or the logic that needs to be put in. Some of the other products struggle in this aspect. They cannot do things in a certain way, or they have a product limitation, whereas, with webMethods, I have never faced this kind of problem."

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

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

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

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

"In terms of improvement, it would be better if it adapted quicker to open standards. It took a while for API specification before the last version was available. The spec of version two was rather quick."

"The stability of the various modules of the product suite have been a bit of a concern lately. Though their support team is always easy to reach out to, I would prefer it not come to that."

"We need more dashboards and reporting engines that can provide detailed information for management. In short, we need better analytics."

"webMethods Integration Server could improve on the version control. I'm not sure if Web Method has some kind of inbuilt integration with Bitbucket or GitHub or some kind of version control system. However, that's one area where they can improve."

"The certifications and learning resources are not exposed openly enough. For instance, they have a trial version which comes with only a few basic features, and I think that community-wise they need to offer more free or open spaces where developers can feel encouraged to experiment."

"The patching of infrastructure is not very smooth and improved authentication should be added in the next feature."

"Scalability and connectors to different cloud applications is lacking."

"I am not satisfied with the solution because it takes too much effort to migrate and add new information. The migration could be easier."

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

"I do see a lack of capabilities inside of the monetization area for them. They have a cloud infrastructure that is pay per use type of a thing. If you already use 1,000 transactions per se, then you can be charged and billed. I see room for improvement there for their side on that particular capability of the monetization."

"The price is a little bit high, especially regarding their support."

"It is a cost-effective solution."

"There is a license needed to use the webMethods Integration Server."

"I would like to see better pricing for the license."

"There are no hidden costs in addition to the standard licensing fees for webMethods. For corporate organizations, it's a very cheap or fairly priced product, but for growing or small businesses, it's quite expensive. These businesses would probably need to consider an enterprise services bus at some point. Thus, from a pricing point, it closes out non-cooperate businesses."

"The solution's development license is free for three to six months. We have to pay for other things."

"Based on our team discussions and feedback, it is pretty costly because they charge us for each transmission."