You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@airflow.apache.org by "Ash Berlin-Taylor (JIRA)" <ji...@apache.org> on 2019/02/26 15:08:02 UTC
[jira] [Closed] (AIRFLOW-3798) Workflow management for user driven
business processes
[ https://issues.apache.org/jira/browse/AIRFLOW-3798?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ash Berlin-Taylor closed AIRFLOW-3798.
--------------------------------------
Resolution: Information Provided
> Workflow management for user driven business processes
> ------------------------------------------------------
>
> Key: AIRFLOW-3798
> URL: https://issues.apache.org/jira/browse/AIRFLOW-3798
> Project: Apache Airflow
> Issue Type: Wish
> Reporter: Tushar
> Priority: Major
>
> We are evaluating workflow management engines. We have use cases for machine operated tasks as well as user-driven business processes. Airflow appears to be the most popular workflow management engine for cloud operations. However, it doesn't appear to be a good choice, if tasks are performed by users and may take days/ months to be completed. Since the state of tasks are always represented by a corresponding in-memory and running processes (operator/DAG instance etc.). & thus, consuming unnecessary compute cycles for our cases.
> Please share, if
> 1) is it possible to manage long-running tasks without hogging CPU cycles in airflow?
> 2) can the airflow architecture be extended for such type of use cases by putting in an event bus and events?
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)