Apache Airflow is an open source tool that can be used to programmatically author, schedule and monitor data pipelines using Python and SQL.
N/A
Camunda
Score 8.0 out of 10
N/A
Camunda is a process orchestration tool designed to help organizations design, automate, and improve any process. Built for business and IT collaboration using BPMN and DMN standards, Camunda aims to enable seamless integration across endpoints to transform mission-critical processes.
N/A
Pricing
Apache Airflow
Camunda
Editions & Modules
No answers on this topic
Self-Managed Enterprise
Contact Sales
per year
SaaS Enterprise
Contact Sales
per year
Offerings
Pricing Offerings
Apache Airflow
Camunda
Free Trial
No
Yes
Free/Freemium Version
Yes
Yes
Premium Consulting/Integration Services
No
No
Entry-level Setup Fee
No setup fee
No setup fee
Additional Details
—
—
More Pricing Information
Community Pulse
Apache Airflow
Camunda
Considered Both Products
Apache Airflow
Verified User
Anonymous
Chose Apache Airflow
Step functions are only available in AWS but Apache Airflow provides cross cloud access. Apache Airflow also provides flexibility to pause, start and re-trigger dags. Provides executors where we can run in-house calculations if needed and which requires no integration with …
Apache Airflow is suited for a much wider set of use cases compared to Databricks. You can run it anywhere, and there is also no vendor lock-in. With Airflow, we can utilize almost any compute engine. Same thing we want to do with Databricks. There might be some level of …
Multiple DAGs can be orchestrated simultaneously at varying times, and runs can be reproduced or replicated with relative ease. Overall, utilizing Apache Airflow is easier to use than other solutions now on the market. It is simple to integrate in Apache Airflow, and the …
Using Jenkins and Kafka, it is not for the same purpose, although it might be similar. I would say AirFlow is really what it says on the can - workflow management. For our organisation, the purpose is clear. So long your aim is to have a rich workflow scheduler and job …
Much easy to deploy Apache Airflow as opposed to other products, with flexible deployment options as well as flexible integration with other tools and platforms.
There are a number of reasons to choose Apache Airflow over other similar platforms- Integrations—ready-to-use operators allow you to integrate Airflow with cloud platforms (Google, AWS, Azure, etc) Apache Airflow helps with backups and other DevOps tasks, such as submitting a …
digdag (https://www.digdag.io/)- Digdag is a very simple build, run, schedule, and monitor complex pipelines of tasks with a simple implementation and no configuration. Easy to write YAMLs
Airflow has a better community and widely adopted. Has a better UI and better documentation
Overall using Apache Airflow is easy to use compare than other other tools available in the market, It is easy to integrate in apache airflow and the workflow can be monitored and scheduling can be done easily using apache airflow, recommend this tool for Automating the data …
They're just different products with different target audiences. In different ways, IBM and Pega have offerings that are meant to serve processes in a platform-centric approach to their customers. An emphasis on unified development environments, including forms building, …
Lacks good documentation. Training and documentation is geared towards those who are already technically adept. Does not have as many data integrations as other full fledged products. Paid version of Camunda is not as fully fledged as other products.
For a quick job scanning of status and deep-diving into job issues, details, and flows, AirFlow does a good job. No fuss, no muss. The low learning curve as the UI is very straightforward, and navigating it will be familiar after spending some time using it. Our requirements are pretty simple. Job scheduler, workflows, and monitoring. The jobs we run are >100, but still is a lot to review and troubleshoot when jobs don't run. So when managing large jobs, AirFlow dated UI can be a bit of a drawback.
Camunda Platform is well suited for scenarios where there are different stages in a business flow and the flow is driven by user action at each stage. For example placing of an order on an ecommerce platform. Depending on whether user was able to make the payment or not the workflow would go to dispatch or retry stage. Now the retry stage would trigger further actions like sending follow up emails etc. Likewise, dispatch stage would have a different set of actions. Since every order is important and we need to know where it stands, using Camunda Platform is imperative. Camunda Platform might not be a right choice where just a one off thing needs to be done. For example, uploading of product information by user or periodic processing of heavy images by a worker. These are all either one step processes or periodic automated processes where we can track the status without using a business modeler like Camunda Platform.
Apache Airflow is one of the best Orchestration platforms and a go-to scheduler for teams building a data platform or pipelines.
Apache Airflow supports multiple operators, such as the Databricks, Spark, and Python operators. All of these provide us with functionality to implement any business logic.
Apache Airflow is highly scalable, and we can run a large number of DAGs with ease. It provided HA and replication for workers. Maintaining airflow deployments is very easy, even for smaller teams, and we also get lots of metrics for observability.
Documentation - It is usually daunting for beginners because of lack of good documentation
Simplified setup on local machine for Camunda Server would help developers test changes quickly
Easier migration from one deployment version of a Camunda process to another deployment version would help in making changes and deploying them faster.
Heap memory management becomes issue at times resulting in stuck processes. This needs to be resolved.
For its capability to connect with multicloud environments. Access Control management is something that we don't get in all the schedulers and orchestrators. But although it provides so many flexibility and options to due to python , some level of knowledge of python is needed to be able to build workflows.
Apache Airflow is suited for a much wider set of use cases compared to Databricks. You can run it anywhere, and there is also no vendor lock-in. With Airflow, we can utilize almost any compute engine. Same thing we want to do with Databricks. There might be some level of difficulty based on the support.