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."Designing processes and workflows is easier, and it assists in coordinating all of the different processes."
"Since the solution is programmatic, it allows users to define pipelines in code rather than drag and drop."
"Every feature in Apache Airflow is valuable. The number of operators and features I've used are mainly related to connectivity services and integrated services because I primarily work with GCP."
"The product integrates well with other pipelines and solutions."
"The solution's UI allows me to collect all the information and see the code lines."
"The reason we went with Airflow is its DAG presentation, that shows the relationships among everything. It's more of a configuration-driven workflow."
"Since it's widely adopted by the community, Apache Airflow is a user-friendly solution."
"Development on Apache Airflow is really fast, and it's easy to use with the newer updates. Everything is in Python, so it's not hard to understand. They also have a graphical view, so if you are not a programmer and you are just an administrator, you can easily track everything and see if everything is working or not."
"The Process Designer is good. We like how we can drag and drop and link the processes up, that works out great for us."
"Our customers use the solution as a workflow platform to manage their processes."
"Stability-wise, I rate the solution a ten out of ten."
"It is easy to take a requirement, put it in the code, and deploy it."
"It helps maintain, and in many instances, lower costs, as well as to maintain those costs, keeping them stable."
"Technical support is pleasant to work with and always available."
"The most valuable features are the integration capabilities - BPM can connect with almost any legacy or advanced system."
"The most valuable feature for the organization is the Document Store."
"We need to develop our workflow description and notations because out of the box, Apache Airflow does not provide some features that are needed."
"I want to see Apache Airflow have more integrations with more production-based databases since it is an area where the product lacks currently."
"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."
"There is a need for more features on experimental evolution steps."
"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."
"We're currently using version 1.10, but I understand that there's a lot of improvements in version 2. In the earlier version that we're using, we sometimes have problems with maintenance complexity. Actually using Airflow is okay, but maintaining it has been difficult."
"Apache Airflow should have better integration with cloud platforms."
"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."
"We had a weird problem that whenever the database would go down, even for a few seconds, it broke the connection. It would not come back up as it was supposed to. However, working with IBM, we were able to figure out a fix, then it came back up, even after an interruption of the database."
"I would like to see the front-end support improved because it should be fully integrated and supported."
"I would like it more documentation during the design phase."
"IBM BPM's price could be improved."
"New users will need at least six months to get comfortable with IBM BPM, at least initially. So, there's a learning curve."
"Process Server is no more available than new products out there, but in general IBM has a high cost and complex setup."
"Needs better reporting. I do not think that we are fully taking advantage of what it already has yet."
"They should incorporate an API gateway functionality within it to simplify integrations."
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, Appian, Pega BPM, IBM Business Automation Workflow and ServiceNow Orchestration. 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.