Spring Cloud Data Flow vs webMethods.io comparison

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

"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 best thing I like about Spring Cloud Data Flow is its plug-and-play model."

"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 product supports various types of digital documents, including XMLs and EDI."

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

"The product is powerful, straightforward, and easy to use."

"Oracle's self-service capabilities, of which we make extensive use, is the most valuable feature."

"It's very flexible and a good platform to use."

"The MFT component of webMethods, for example, is easy to set up and convenient to use. It handles files very efficiently and it is easy to automate tasks with complex schedules. Monitoring is centralized to MWS which can be used to monitor other products as well (Trading Networks, BPM, MFT, etc.)"

"It frankly fills the gap between IT and business by having approval and policy enforcement on each state and cycle of the asset from the moment it gets created until it is retired."

"The development is very fast. If you know what you're doing, you can develop something very easily and very fast."

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

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

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

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

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

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

"They should develop clear visibility for the onboarding."

"The learning curve is a little steep at first."

"We'd like for them to open up to a more cloud-based solution that could offer more flexibility and maybe a better rules engine or more integration with rules engines."

"Support is expensive."

"The logging capability has room for improvement. That way, we could keep a history of all the transactions. It would be helpful to be able to get to that without having to build a standalone solution to do so."

"It is difficult to maintain."

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

"wM SAP Adapter User Guide - Example, like Message Broker setup was unclear, leading to issues during Testing and we had refer the internet forums to understand that there is a Message Broker Cleanup utility and that needs to be setup as well."

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

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

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

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

"The product is expensive."

"I don’t have much idea about prices, but webMethods API Portal is not something cheaper."

"It is expensive, but we reached a good agreement with the company. It is still a little bit expensive, but we got a better deal than the previous one."

"webMethods Integration Server is expensive, and there's no fixed price on it because it has a point pricing model. You can negotiate, which makes it interesting."

"Currently, the licensing solution for this product is pretty straightforward. The way that Software AG has moved in their licensing agreements is very understandable. It is very easy for you to see where things land. Like most vendors today, they are transaction based. Therefore, just having a good understanding of how many transactions that you are doing a year would be very wise. Luckily, there are opportunities to work with the vendor to get a good understanding of how many transactions you have and what is the right limit for you to fall under."

"I do think webMethods is coming under increasing pressure when it comes to their price-to-feature value proposition. It's probably the single biggest strategic risk they have. They're very expensive in their industry. They've been raising the price recently, especially when compared with their competitors."

"The product is very expensive."