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 solution's UI allows me to collect all the information and see the code lines."
"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."
"Since the solution is programmatic, it allows users to define pipelines in code rather than drag and drop."
"The best feature is the customization."
"The product is stable."
"Apache Airflow is in Python language, making it easy to use and learn."
"We're running it on a virtual server, which we can easily upgrade if needed."
"When our clients automate the KYC and onboarding processes, they can reduce their manual force and then deploy them in much better tasks rather than the mundane activities of selecting forms and gathering information."
"Pega BPM's most valuable feature is the use of CDX to solve problems."
"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 most valuable aspect of the solution is the various workflows."
"While Pega technical support is okay, it also depends on the issues you need help with and who your contact is with Pega."
"This is a customizable product."
"The case management is great."
"Pega BPM offers a lot of out-of-the-box functionalities."
"The dashboards could be enhanced."
"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 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 cannot run real-time jobs in the solution."
"The platform's stability needs improvement, particularly regarding occasional interruptions due to networking issues."
"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."
"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."
"Enhancements become necessary when scaling it up from a few thousand workflows to a more extensive scale of five thousand or ten thousand workflows."
"Pega is claiming they're into low code but as per Gartner Magic Quadrant, Pega is not there now."
"Pega Cloud early adoption and use for cross enterprise capability was new to many. The early adoption meant version 2.0 of their cloud service may require refactoring and redesign of some services."
"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."
"Pega should work on redefining their model and creating a demand for their skills."
"It needs more integration with other platforms."
"It's called a local platform but on the other hand, it needs a lot of experience. It's not all that easy to click and plug and play. If you really want to use all the features out of this platform, you definitely need a lot of experience and a lot of training to get there."
"The local development approach is good in Pega, however, cost-wise, it's getting expensive. That needs to be addressed."
"What should be included is some UI features and maybe some integrations. This includes documentation on how the UI works."
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 55 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 "Low code with great APIs and good flexibility". Apache Airflow is most compared with Camunda, Informatica Cloud API and App Integration, IBM BPM, IBM Business Automation Workflow and Appian, 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.