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."I found the following features very useful: DAG - Workload management and orchestration of tasks using."
"The user interface for monitoring and managing workflows has been excellent, particularly in the latest version. c"
"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."
"Apache Airflow is in Python language, making it easy to use and learn."
"Apache Airflow is easy to use and can monitor task execution easily. For instance, when performing setup tasks, you can conveniently view the logs without delving into the job details."
"The solution is flexible for all programming languages for all frameworks."
"We're running it on a virtual server, which we can easily upgrade if needed."
"Its user-friendly interface makes it straightforward to operate, offering a plethora of features for data preparation, buffering, and format conversion."
"Case Management, as well as Workflow Automation, are Pega's most powerful capabilities."
"Pega is a local platform that has evolved from a BPM perspective. This allows teams using this solution to address complexities without having deep knowledge in a specific development area."
"The most valuable features of Pega BPM are low code, no code, functionality, and easy development."
"The ability to define processes, build reports, and get insights or analytics on data is most valuable. It is a powerful platform."
"The product helps you to build faster."
"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."
"Pega BPM's most valuable features are case management, integration, the convenience of using REST APIs, and the ease of changing things at the UI level."
"The tool reduces our costs."
"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."
"Apache Airflow should have better integration with cloud platforms."
"For admins, there should be improved logging capabilities because Apache Airflow does have logging, but it's limited to some database data."
"The dashboard is connected into the BPM flow that could be improved."
"Apache Airflow could be improved with the addition of more frameworks."
"UI can be improved with additional user-friendly features for non-programmers and for fewer coding practitioner requirements."
"We need to develop our workflow description and notations because out of the box, Apache Airflow does not provide some features that are needed."
"The scalability of the solution itself is not as we expected. Being on the cloud, it should be easy to scale, however, it's not."
"The local development approach is good in Pega, however, cost-wise, it's getting expensive. That needs to be addressed."
"In the next release of Pega BPM, they should add more ways to do the customer interaction fields in the portals."
"The cost of licensing could be improved."
"This is a quite expensive product."
"If it could also be integrated with robotics, it could help with a lot of things, even if we don't have APIs, we could still talk to other applications. If it could invoke a bot, for example."
"Currently, there isn't any feature I want to be added in the next release of Pega BPM because Pega always adds new features that my team welcomes and looks forward to learning. One area for improvement in the solution is the long learning curve, but after that, you'll find Pega BPM easy to use."
"One of the areas of this solution that could be improved would be to advance the low code features of the application itself. We would also like to use the same platform to build any application, even if it is not necessarily defined as a functionality needed by a BPM."
"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."
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.