We performed a comparison between Apache Airflow and webMethods Integration Server based on real PeerSpot user reviews.
Find out what your peers are saying about Camunda, Apache, Pega and others in Business Process Management (BPM)."The UI is very simple and easy to learn."
"The reason we went with Airflow is its DAG presentation, that shows the relationships among everything. It's more of a configuration-driven workflow."
"The solution is quite configurable so it is easy to code within a configuration kind of environment."
"One of its most valuable features is the graphical user interface, providing a visual representation of the pipeline status, successes, failures, and informative developer messages."
"The best part of Airflow is its direct support for Python, especially because Python is so important for data science, engineering, and design. This makes the programmatic aspect of our work easy for us, and it means we can automate a lot."
"The most valuable feature of Apache Airflow is creating and scheduling jobs. Additionally, the reattempt at failed jobs is useful."
"Apache Airflow's best feature is its flexibility."
"The solution's UI allows me to collect all the information and see the code lines."
"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.)"
"The product is very stable."
"Given that you have one integration API in place, it takes very minimal effort to scale it to any other application that might want to use the same. Its flow-based development environment is a breeze and makes it really easy to re-use most of the existing components and build up a new API."
"What I found most valuable in webMethods Integration Server is that it's a strong ESB. It also has strong API modules and portals."
"Application integration, business process integration, and B2B partner integration are valuable. But among these, I feel B2B partner integration is the most valuable. This module integrates two business partners and exchanges data through electronic data interchange messages in the form of specific standards, without any manual process needed."
"Most of the work in our organization can be more easily done using the tool."
"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 messaging part is the most valuable feature."
"Programmatically, it's very good, and it doesn't have any competitors, but you cannot develop anything in Airflow UI. You need to develop everything within the program. In the market, other tools have come up recently as competitors to Airflow, and they also give graphical programming options, whereas Airflow doesn't provide that feature currently. All the DAGs you want to build need to be coded in Python."
"Apache Airflow should have better integration with cloud platforms."
"Apache Airflow could be improved with the addition of more frameworks."
"Enhancements become necessary when scaling it up from a few thousand workflows to a more extensive scale of five thousand or ten thousand workflows."
"The problem with Apache Airflow is that it is an open-source tool. You have to build it into a Kubernetes container, which is not easy to maintain, and I find it to be very clunky."
"Technical support is an area that needs improvement."
"There is an area for improvement in onboarding new people. They should make it simple for newcomers. Else, we have to put a senior engineer to operate it."
"The solution could be improved by simplifying the integration process."
"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."
"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."
"Need to see more API portal features like monetizing APIs and private cloud readiness."
"Large file handling is pretty hard comparatively to other middleware tools."
"Technical support is an area where they can improve."
"On the monitoring side of things, the UI for monitoring could be improved. It's a bit cumbersome to work with."
"The deployment should be simplified."
"The UI for the admin console is very old. It hasn't been updated for years and is pretty much the same one that we started with. This is something that could be refreshed and made more modern."
More webMethods Integration Server Pricing and Cost Advice →
Apache Airflow is ranked 2nd in Business Process Management (BPM) with 31 reviews while webMethods Integration Server is ranked 3rd in Enterprise Service Bus (ESB) with 60 reviews. Apache Airflow is rated 8.0, while webMethods Integration Server is rated 8.0. The top reviewer of Apache Airflow writes "Enable seamless integration with various connectivity and integrated services, including BigQuery and Python operators ". On the other hand, the top reviewer of webMethods Integration Server writes "Event-driven with lots of helpful formats, but minimal learning resources available". Apache Airflow is most compared with Camunda, Informatica Cloud API and App Integration, IBM BPM and IBM Business Automation Workflow, whereas webMethods Integration Server is most compared with IBM Integration Bus, webMethods.io Integration, Mule ESB, TIBCO BusinessWorks and Boomi AtomSphere Integration.
We monitor all Business Process Management (BPM) 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.