We performed a comparison between Apache Airflow and IBM BPM based on real PeerSpot user reviews.
Find out in this report how the two Business Process Management (BPM) solutions compare in terms of features, pricing, service and support, easy of deployment, and ROI."The best feature is the customization."
"The initial setup was straightforward and it does not take long to complete."
"The UI is very simple and easy to learn."
"Since it's widely adopted by the community, Apache Airflow is a user-friendly solution."
"Apache Airflow's best feature is its flexibility."
"The reason we went with Airflow is its DAG presentation, that shows the relationships among everything. It's more of a configuration-driven workflow."
"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."
"I like the UI rework, it's much easier."
"The performance is fine."
"The solution is stable."
"There is a component of this BPM pool - I can't recall the name. What it does is, it allows you to create various scenarios and then run them quickly, before actually putting them onto a tool. So I think that part of the tool is really fantastic, because that enables you to create scenarios, create simulations, before actually going out and putting it into the tool itself"
"One of the reasons for adopting this solution ten years ago was its ease of use. It had a lot of off-the-shelf functionality, and it did not need to be developed specifically for the project that we were implementing. That was the main reason for adopting it in the beginning."
"We made the transformation to agile. Altogether with BPM, it is the total package."
"IBM BPM is stable."
"IBM BPM is equipped with all the functionalities which are needed for building BPM enterprise-level applications."
"It continues to keep up with the changing needs of the business. That is the strong value proposition of BPM. It's not a one-time automation."
"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."
"The dashboards could be enhanced."
"We have faced scenarios where Apache Airflow becomes non-responsive, leading to job failures. To resolve such situations, we had to manually reboot Apache Airflow since it doesn't provide an option to restart within the application. This necessitated modifying some configurations to initiate a restart of all Apache Airflow components. Although Apache Airflow is generally dependable, it may occasionally encounter glitches that can disrupt production flows and batches."
"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."
"The graphical user interface can be improved."
"The documentation must be improved."
"The platform's stability needs improvement, particularly regarding occasional interruptions due to networking issues."
"UI can be improved with additional user-friendly features for non-programmers and for fewer coding practitioner requirements."
"IBM BPM needs to have a better and modified interface."
"We need process monitoring. It is somewhat complex to monitor all the processes which work."
"The engine itself tends to accumulate a lot of data that needs to be cleaned up, and that's the kind of thing that keeps it from, in some scenarios, scaling as much as it needs to. And then, when you're building solutions, if you're not careful to keep the screens from being associated with too much data, if you're going to just do things the way that a lot of people would just assume that they can do, without having experience of having made those mistakes before, it will accumulate a lot of data, and that will cause it to perform very badly."
"The integration could be improved."
"Some of the features are not enough for my business. We need to build custom user management for the many end users affected by BPM."
"It is not user-friendly."
"We still have a couple of issues that we are working on right now with stability. Mostly on the configuration side of the tool, and it has been about a month that we have been working to stabilize the platform."
"We would like better performance and more visibility on each step of the tool."
Apache Airflow is ranked 2nd in Business Process Management (BPM) with 31 reviews while IBM BPM is ranked 5th in Business Process Management (BPM) with 105 reviews. Apache Airflow is rated 8.0, while IBM BPM is rated 7.8. 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 IBM BPM writes "Offers good case management and its integration with process design but there's a learning curve". Apache Airflow is most compared with Camunda, Informatica Cloud API and App Integration, IBM Business Automation Workflow, AWS Step Functions and Bizagi, whereas IBM BPM is most compared with Camunda, Pega BPM, Appian, IBM Business Automation Workflow and AWS Step Functions. See our Apache Airflow vs. IBM BPM report.
See our list of best Business Process Management (BPM) vendors.
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.