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
AppFog (discontinued)
Score 6.6 out of 10
N/A
AppFog was a cloud-agnostic application and infrastructure management platform used to manage workloads across on-premises and third-party cloud environments. It has been discontinued.
$0
Pricing
Apache Airflow
AppFog (discontinued)
Editions & Modules
No answers on this topic
No answers on this topic
Offerings
Pricing Offerings
Apache Airflow
AppFog (discontinued)
Free Trial
No
No
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
AppFog (discontinued)
Features
Apache Airflow
AppFog (discontinued)
Workload Automation
Comparison of Workload Automation features of Product A and Product B
Apache Airflow
8.7
12 Ratings
5% above category average
AppFog (discontinued)
-
Ratings
Multi-platform scheduling
9.312 Ratings
00 Ratings
Central monitoring
8.912 Ratings
00 Ratings
Logging
8.612 Ratings
00 Ratings
Alerts and notifications
9.312 Ratings
00 Ratings
Analysis and visualization
6.712 Ratings
00 Ratings
Application integration
9.412 Ratings
00 Ratings
Platform-as-a-Service
Comparison of Platform-as-a-Service features of Product A and Product B
Airflow is well-suited for data engineering pipelines, creating scheduled workflows, and working with various data sources. You can implement almost any kind of DAG for any use case using the different operators or enforce your operator using the Python operator with ease. The MLOps feature of Airflow can be enhanced to match MLFlow-like features, making Airflow the go-to solution for all workloads, from data science to data engineering.
It was very good to use in small scale projects. Considering the high end projects with many instances and multi-platform architectures, it is better to test before the application is deployed. I think few of the questions can be general - who are the system users and what size is the application focussing on? How much resources are required? Will the application require any additional services?
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.
UI/Dashboard can be updated to be customisable, and jobs summary in groups of errors/failures/success, instead of each job, so that a summary of errors can be used as a starting point for reviewing them.
Navigation - It's a bit dated. Could do with more modern web navigation UX. i.e. sidebars navigation instead of browser back/forward.
Again core functional reorg in terms of UX. Navigation can be improved for core functions as well, instead of discovery.
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.
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 workflow can be monitored and scheduling can be done quickly using Apache Airflow. We advocate using this tool for automating the data pipeline or process.
Primarily because it used to have a good free tier earlier, which it does not anymore. It's simple, and things are available to use. Compared to it's competitors, it does has less features, but that kind of acts in its favor. That adds to the simplicity, and ease of use for a new user.
Impact Depends on number of workflows. If there are lot of workflows then it has a better usecase as the implementation is justified as it needs resources , dedicated VMs, Database that has a cost