We performed a comparison between Apache Airflow and Appian 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."We're running it on a virtual server, which we can easily upgrade if needed."
"The most valuable feature of Apache Airflow is creating and scheduling jobs. Additionally, the reattempt at failed jobs is useful."
"Since Apache works very well on Python, we can manage everything and create pipelines there."
"Designing processes and workflows is easier, and it assists in coordinating all of the different processes."
"The solution is quite configurable so it is easy to code within a configuration kind of environment."
"The product integrates well with other pipelines and solutions."
"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."
"I found the following features very useful: DAG - Workload management and orchestration of tasks using."
"Write to Data Store Entity - Saving data in SQL databases is done easily using entities. Entities (CDTs in Appian terminology) define relationships and target schema tables via XSD files."
"Appian has many valuable features, the first being the ease of development—rapid development. Second, the process of learning the product and tool is faster when compared to its peers in the market. It's closer to low-code, and while it's still not very easy, it's more low-code than other products in the industry. Appian has a good user interface, a seamless model user interface, which comes without additional coding. It can also integrate with multiple systems."
"It has created executable requirements and speeds up the SDLC process greatly."
"The low code functionality and being able to get applications faster to customers or to the market are valuable."
"Another advantage of this tool is its reports and records. You can maintain dashboards, layouts. If you with a Java solution, it takes six months time. If you use this tool, you can finish in one or one and a half months' time."
"Process culture is making noise inside the organization because now, everybody knows that their time is being monitored."
"The application life cycle is very clear. I started learning it and giving some workshops to my team. Creating the users and the building is very structured. Documentation is nice and it's easy to learn."
"The agile manner that we require to create our workflows. This is probably the most critical part of our solution and the time it takes to start processing the solution."
"Technical support is an area that needs improvement."
"Adding more automated components in Apache Airflow for basic things like exporting the data would be helpful."
"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 graphical user interface can be improved."
"We cannot run real-time jobs in the solution."
"The documentation must be improved."
"The solution could be improved by simplifying the integration process."
"We need to develop our workflow description and notations because out of the box, Apache Airflow does not provide some features that are needed."
"One room for improvement is the ease of UI UX development, like in OutSystems and Mendix."
"Form creation and SAIL proprietary language still basically require programming. The claim a BA type can do everything is hogwash."
"If we could calculate the amount of data that will be realized, it would help us a lot."
"There is no UI customization possible."
"It would be useful if they could create an academy or forum in the future to help active users answer questions they have about the solution."
"The tool itself is pretty good, but the main area that we struggled with was the backend. The frontend development is really good, but the backend modeling can be streamlined a little bit. There are good integrations, but tying them through the data layer and then up into the frontend could be improved a little bit. It does read/write on the data source, and you can configure it to just write or just read, but there is a little bit of work involved."
"The solution could improve robotic process automation."
"There are some restrictions with respect to using external components within Appian. So, for example, if we do not have a particular feature available, there's a long cycle of getting approvals and all of that. That does not offer flexibility, which definitely can be improved on."
Apache Airflow is ranked 2nd in Business Process Management (BPM) with 31 reviews while Appian is ranked 4th in Business Process Management (BPM) with 57 reviews. Apache Airflow is rated 8.0, while Appian is rated 8.4. 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 Appian writes "Low resource consumption, easy setup, and stable". Apache Airflow is most compared with Camunda, Informatica Cloud API and App Integration, IBM BPM, IBM Business Automation Workflow and Oracle BPM, whereas Appian is most compared with Microsoft Power Apps, OutSystems, Camunda, ServiceNow and Pega BPM. See our Apache Airflow vs. Appian 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.
