Flyte enables production-grade orchestration for machine learning workflows and data processing created to accelerate local workflows to production.

Flyte

We're considering switching from Nextflow to Flyte. Looking at some of the questions above it seems that deep knowledge of k8s is needed to work with flyte. Does anyone moved from Nextflow and think it was the right choice?

I'm not familiar with Nextflow, but it might be possible to support a Nextflow plugin in Flytekit, allowing for quicker and more seamless integration.

Here's airflow agent's example:
<https://docs.flyte.org/en/latest/flytesnacks/examples/airflow_agent/airflow_agent_example_usage.html>

Or maybe integrate the old pipeline by raw container tasks.
<https://docs.flyte.org/en/latest/user_guide/customizing_dependencies/raw_containers.html#raw-container>

raw container tasks support local execution, so it will not be painful.

There are many that have migrated and are happy

If k8s expertise is a question, consider <http://union.ai|union.ai>, we manage Flyte plus extended in your cloud

Thanks for the reply guys. Nextflow is competing orchestration software that's very common in biotech. However, it's quite annoying and gets in a way. I'll give flyte a go