We performed a comparison between Apache Airflow, IBM BPM, and IBM Case Foundation based on real PeerSpot user reviews.
Find out what your peers are saying about Camunda, Apache, Pega and others in Business Process Management (BPM)."It's stable."
"I found the following features very useful: DAG - Workload management and orchestration of tasks using."
"The UI is very simple and easy to learn."
"Its user-friendly interface makes it straightforward to operate, offering a plethora of features for data preparation, buffering, and format conversion."
"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."
"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."
"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."
"Apache Airflow is useful for workflow automation, making it capable of automating pipelines, data pipelines, and data warehouse processes."
"We use the solution to develop and deliver products."
"It has reduced a lot of manual errors and processes."
"By automating several tasks, we have already reduced a lot of work for the business."
"The installation was straightforward."
"Integration is a big plus for me."
"It helps maintain, and in many instances, lower costs, as well as to maintain those costs, keeping them stable."
"The system integration layer is valuable because this enables an organization to create a single point where all the key organizational master data is held in different IT applications across different functions, that can be accessed and updated."
"It's a solid product. It covers most of the pain points for clients."
"It is easy to set up workflows that notify the user depending on certain events."
"The most valuable feature is its stability, which is why we are using it."
"The content management is great."
"It's very easy."
"The most valuable features are those involving decision making, analysis, and anything related to event documents because those processes are related to content as well."
"The most valuable feature is the content manager part of the file as it is very stable, robust, and reliable."
"The solution is scalable."
"Flexible and the ability to divide search screens, and to search for documents. The ECM feature inside the system is great."
"For admins, there should be improved logging capabilities because Apache Airflow does have logging, but it's limited to some database data."
"The platform's stability needs improvement, particularly regarding occasional interruptions due to networking issues."
"Technical support is an area that needs improvement."
"Apache Airflow could be improved by integrating some versioning principles."
"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 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'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 a need for more features on experimental evolution steps."
"Stability wavers. We have some opportunities for improvement in this space, especially as we approach our target volume of a million transactions a day. It is tough, because it is not necessarily the product. It is more around the platform and infrastructure to support it, so the connectivity to the database, web sessions, and reverse proxies in front of that."
"Needs better reporting. I do not think that we are fully taking advantage of what it already has yet."
"From the testing perspective and minor enhancements perspective, customization is something that is a little tedious as compared to new tools. In addition, various open-source tools that are available are not working with IBM BPM."
"We would like better performance and more visibility on each step of the tool."
"Importing and exporting between multiple environments is more difficult with other tools."
"Where it can be improved is Integration. I think that the direction that IBM is taking now, to have something that is much more integrated, that can be seen as one single solution, is clearly the right way."
"I would like to see more inclusion of RPA technologies. If we have more manual processes, we can use robotic process automation and integrate that in with the solution."
"The coaches and the user interface are the areas that can be improved a lot. It is good in terms of data processing, but the UI, scripting, and coaches are not very user-friendly and developer-friendly. Performance is always an issue. The scripting and the pattern that it uses are very tedious for new developers to understand, and it takes time to master it in depth. When comparing IBM BPM with IBM APN, a lot of things are provided out of the box in IBM APN. We don't have to write code or a Java connector to make a functionality work. It would be very helpful and time-saving for developers if IBM BPM is improved in this area to provide many functionalities or drag-and-drop options so that the developers don't have to write the code."
"The solution can be quite expensive."
"We are now using microservices but there are some areas where the coordination with FileNet is problematic."
"Once a workflow is launched then it stays static forever, which is a problem because if there is a change in the business then you cannot change the workflow."
"The place of improvement is merging or combining all of the workflow functionality into one seamless tool. Now, there are multiple installations that are different. Case Foundation, before you can put Case Manager and you've got IBM BPM, and the roadmap is there to merge them altogether. But that's the struggle at the moment, it's having multiple installations and disparate workflow applications."
"The service as it currently stands is out-of-date and lacks flexibility."
"The interface needs to be more user-friendly."
"There is a need for more open and flexible integration capabilities, allowing seamless collaboration with a broader spectrum of business process management solutions, beyond the confines of IBM's document management offerings."
"Comparing the solution with other interfaces, IBM BPM is much better than Case Foundation. They need to make this solution's interface more user-friendly."
