Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Why ecFlow rather than Airflow? #4

Closed
Mo-Dabao opened this issue Jan 19, 2021 · 3 comments
Closed

Why ecFlow rather than Airflow? #4

Mo-Dabao opened this issue Jan 19, 2021 · 3 comments

Comments

@Mo-Dabao
Copy link

Are there any specific tasks that only ecFlow can do?

@Mo-Dabao Mo-Dabao changed the title Why ecFlow rather then Airflow? Why ecFlow rather than Airflow? Jan 19, 2021
@avi369
Copy link
Contributor

avi369 commented Jan 19, 2021 via email

@iainrussell
Copy link
Member

Hello,

Just to add to what Avi said, we looked at different packages in 2019, and found that there are many similarities between them, but ecFlow still provided us with more flexibilities in certain areas, e.g. in the richness of trigger expressions. Its GUI is also extremely fully-featured, but it is a desktop application (Linux and macOS), not a web application. This is good for us, but maybe not ideal for everyone.
 
In the end, if your workflows are not very complicated, then probably any workflow manager would be ok. We develop and use ecFlow because it has been designed with our needs in mind (ECMWF, our Member and Co-operating States and other customers). You will probably only understand the limitations of each system by trying them.
 
Best regards,
Iain

@Mo-Dabao
Copy link
Author

Thanks for the explaination.

It seems that Airflow is more friendly for a python user.

I'll fiddled with ecFlow later.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants