We performed a comparison between Spring Cloud Data Flow and webMethods Integration Server based on real PeerSpot user reviews.
Find out in this report how the two Data Integration solutions compare in terms of features, pricing, service and support, easy of deployment, and ROI."The product is very user-friendly."
"The most valuable feature is real-time streaming."
"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."
"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."
"Some of the key features are the integration platform, query mechanism, message handling within the bus, and the rules engine. We've had a really good experience with webMethods Integration Server."
"We can arrange data caching and look at the solid state. Also, the API gateway is a very good component that can handle relevant cachings and integrations, as well as and also load permitting."
"I would say the core Web-based integrations work the best. They are the most efficient and robust implementations one can do with webMethods."
"It has a good integration server, designer, and a very good API portal."
"How simple it is to create new solutions."
"When it comes to the user interface, I'm already really used to it. I cannot say anything against it. For me, it's easy to use."
"The stability is good."
"The most valuable feature of the webMethods Integration Server is its reliability. It has a lot of great documentation from the service providers. Additionally, it is easy to use."
"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."
"On the tool's online discussion forums, you may get stuck with an issue, making it an area where improvements are required."
"Some of the features, like the monitoring tools, are not very mature and are still evolving."
"The configurations could be better. Some configurations are a little bit time-consuming in terms of trying to understand using the Spring Cloud documentation."
"We need more dashboards and reporting engines that can provide detailed information for management. In short, we need better analytics."
"I would like to see the price improve."
"Version control is not very easy. The packages and the integration server are on Eclipse IDE, but you can't compare the code from the IDE. For example, if you are working on Java code, doing version control and deployment for a quick comparison between the code isn't easy. Some tools or plug-ins are there, such as CrossVista, and you can also play with an SVN server where you have to place your package, and from there, you can check, but you have to do that as a separate exercise. You can't do it from the IDE or webMethods server. You can't just right-click and upload your service."
"This solution could be improved by offering subscription based licensing."
"The initial setup of the webMethods Integration Server is not easy but it gets easier once you know it. It is tiresome but not difficult."
"The deployment should be simplified."
"It would be nice if they had a change management system offering. We built our own deployer application because the one built into webMethods couldn't enforce change management rules. Integration into a change management system, along with the version control system, would be a good offering; it's something that they're lacking."
"This is a great solution and the vendor could improve the marketing of the solution to be able to reach more clients."
More webMethods Integration Server Pricing and Cost Advice →
Spring Cloud Data Flow is ranked 28th in Data Integration with 5 reviews while webMethods Integration Server is ranked 3rd in Enterprise Service Bus (ESB) with 60 reviews. Spring Cloud Data Flow is rated 8.0, while webMethods Integration Server is rated 8.0. The top reviewer of Spring Cloud Data Flow writes "Provides ease of integration with other cloud platforms ". On the other hand, the top reviewer of webMethods Integration Server writes "Event-driven with lots of helpful formats, but minimal learning resources available". Spring Cloud Data Flow is most compared with Apache Flink, Google Cloud Dataflow, Apache Spark Streaming and Azure Data Factory, whereas webMethods Integration Server is most compared with IBM Integration Bus, webMethods.io Integration, Mule ESB, TIBCO BusinessWorks and Boomi AtomSphere Integration. See our Spring Cloud Data Flow vs. webMethods Integration Server report.
We monitor all Data Integration reviews to prevent fraudulent reviews and keep review quality high. We do not post reviews by company employees or direct competitors. We validate each review for authenticity via cross-reference with LinkedIn, and personal follow-up with the reviewer when necessary.
