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."The most valuable feature of Apache Airflow is creating and scheduling jobs. Additionally, the reattempt at failed jobs is useful."
"Its user-friendly interface makes it straightforward to operate, offering a plethora of features for data preparation, buffering, and format conversion."
"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."
"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 initial setup was straightforward and it does not take long to complete."
"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."
"I found the following features very useful: DAG - Workload management and orchestration of tasks using."
"The product integrates well with other pipelines and solutions."
"Overall, the ability to integrate with multiple applications and effective case management is the most valuable."
"The solution provides us with a very good dashboard."
"Pricing is a little on the high side."
"There are a lot of frameworks in the product. I use Pega PRPC the most."
"The most valuable features of the solution are case management, routing, and low-code environment."
"The technical support of Pega BPM is very good."
"The most valuable features of Pega BPM are low code, no code, functionality, and easy development."
"The interface is quite simple and easy to use, even for beginners."
"Adding more automated components in Apache Airflow for basic things like exporting the data would be helpful."
"We cannot run real-time jobs in the solution."
"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 would like to see it more friendly for other use cases."
"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."
"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."
"I want to see Apache Airflow have more integrations with more production-based databases since it is an area where the product lacks currently."
"The documentation must be improved."
"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."
"Business specific functionality is needed."
"The cost of licensing could be improved."
"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."
"I think there is room for improvement in the low code/ no code environment that they're promoting now. That needs to be aligned a little bit more. I still feel that it is not that friendly for a person who has no experience with Pega to just go in and try to create something."
"It is scalable, but it also interacts with a lot of other systems. I think they thought that the interface to other systems, legacy systems, was its strength, but when problems do occur, quickly diagnosing those problems has been a challenge."
"Lack of stronger cloud support is somewhat inconvenient for users and implementation."
"Pega's technical support could be better."
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, IBM BPM, Informatica Cloud API and App Integration, IBM Business Automation Workflow and webMethods Integration Server, whereas Pega BPM is most compared with ServiceNow, Camunda, Appian, IBM BPM and Microsoft Power Apps. 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.