We performed a comparison between Apache Airflow and Pega 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."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 user interface for monitoring and managing workflows has been excellent, particularly in the latest version. c"
"We're running it on a virtual server, which we can easily upgrade if needed."
"The reason we went with Airflow is its DAG presentation, that shows the relationships among everything. It's more of a configuration-driven workflow."
"This is a simple tool to automate using Python."
"Since the solution is programmatic, it allows users to define pipelines in code rather than drag and drop."
"The most valuable feature of Apache Airflow is creating and scheduling jobs. Additionally, the reattempt at failed jobs is useful."
"We have been quite satisfied with the stability of the solution."
"The solution's most valuable feature is its quick setup. Nowhere else you can create a good-looking application this quick. It's a fairly robust system."
"It is a stable product."
"Pega BPM's most valuable feature is the use of CDX to solve problems."
"The solution has very helpful technical support."
"Powerful, full-featured business process management with excellent support"
"The solution is operating well overall."
"It's a good tool for workflow automation."
"The best part of Pega, for me, is that they let you reuse a lot of the aspects in the product."
"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."
"UI can be improved with additional user-friendly features for non-programmers and for fewer coding practitioner requirements."
"Airflow should support the dynamic drag creation."
"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."
"We need to develop our workflow description and notations because out of the box, Apache Airflow does not provide some features that are needed."
"Technical support is an area that needs improvement."
"The dashboards could be enhanced."
"Apache Airflow could be improved by integrating some versioning principles."
"Lack of stronger cloud support is somewhat inconvenient for users and implementation."
"There have been some performance scalability issues. Suppose you want to add more users. You go from, say, 800 users to 1,500 users, and sometimes that creates issues for which there is no clear explanation. To fix it you have to escalate it with customer service and sometimes the response is not up to the mark in resolving those issues."
"What should be included is some UI features and maybe some integrations. This includes documentation on how the UI works."
"The pricing model needs to be improved. Right now, it's too expensive."
"From a technical point of view, it would be helpful to have some advanced analytics to help with configuration. We have a lot of unwanted features and it would be good to configure it more appropriately so that we are using just exactly what we need."
"It should have integration with non-relational databases. A lot of databases are non-relational, and as a company, we are planning to move to NoSQL or open-source databases. It would be good if we are able to install and use Pega on a NoSQL database. They can also try to tailor or organize the company a bit differently and go more towards the microservice concept. I would like Pega to develop machine learning and intelligent AI algorithms. They have a good foundation in terms of the model and the stuff that we are using for some customers, and it will be good to onboard as many machine learning algorithms as possible."
"UI needs improvement."
"The local development approach is good in Pega, however, cost-wise, it's getting expensive. That needs to be addressed."
Apache Airflow is ranked 2nd in Business Process Management (BPM) with 31 reviews while Pega BPM is ranked 3rd in Business Process Management (BPM) with 57 reviews. Apache Airflow is rated 8.0, while Pega BPM is rated 8.2. 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 Pega BPM writes "Provides built-in frameworks that can be reused and reduces time and cost". Apache Airflow is most compared with Camunda, Informatica Cloud API and App Integration, IBM BPM, IBM Business Automation Workflow and Oracle BPM, whereas Pega BPM is most compared with ServiceNow, Camunda, Appian, Microsoft Power Apps and IBM BPM. See our Apache Airflow vs. Pega 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.