Ask HN: What is the simplest data orchestration tool you've worked with?
21–30 of 35 posts
Re: Ask HN: What is the simplest data orchestration tool you've worked with?
#22Re: Ask HN: What is the simplest data orchestration tool you've worked with?
#23Earlier quoted context omitted.
Is there anything even more lightweight, where you don't have to write your code any differently? For instance, say I have 10 jobs that don't depend on each other, all of them pretty small. Dagster and even Luigi feel like overkill but I'd still like to plug those into a unified interface where I can view previous runs, mainly logs and exit codes. Being able to do some light job configuration or add retries would be…
One of the goals of Prefect's SDK is to be minimally invasive from a code-standpoint (in the simplest case you only need two lines to convert a script to a `flow`). Our deployment model also makes infrastructure job config a first-class citizen so you might have a good time trying it out. (disclosure: work at Prefect)
Prefect relies on prefect.task()-wrapped methods as the lowest granularity of concurrency in a program, and requires you to use the (somewhat immature) prefect task APIs to implement that concurrency.
more on this complaint here: https://austinweisgrau.github.io/migrating-to-prefect-part-3...
Re: Ask HN: What is the simplest data orchestration tool you've worked with?
#24Re: Ask HN: What is the simplest data orchestration tool you've worked with?
#25Earlier quoted context omitted.
One of the goals of Prefect's SDK is to be minimally invasive from a code-standpoint (in the simplest case you only need two lines to convert a script to a `flow`). Our deployment model also makes infrastructure job config a first-class citizen so you might have a good time trying it out. (disclosure: work at Prefect)
Love prefect! but for workflows involving concurrency, Prefect code needs to get somewhat invasive. Prefect relies on prefect.task()-wrapped methods as the lowest granularity of concurrency in a program, and requires you to use the (somewhat immature) prefect task APIs to implement that concurrency. more on this complaint here: https://austinweisgrau.github.io/migrating-to-prefect-part-3...
Re: Ask HN: What is the simplest data orchestration tool you've worked with?
#26It's a bit expensive but the only thing they push you to do is to upgrade managed K8S and Airflow once for a while.
Re: Ask HN: What is the simplest data orchestration tool you've worked with?
#27Re: Ask HN: What is the simplest data orchestration tool you've worked with?
#28Terrible answer: cron
Re: Ask HN: What is the simplest data orchestration tool you've worked with?
#29Pure python scripts, maybe using the #%%-convention ( https://code.visualstudio.com/docs/python/jupyter-support-py... ) so you get the best of both notebooks and scripts, in a right-sized instance/container/machine. And if you need to run jobs in parallel, then orchestrate using make, like so: https://www.sumsar.net/blog/makefile-recipe-python-data-pipe...
Yeah, I love this — pure Python with cron or periodic tasks (e.g., Django) works great. Celery task for parallelization, and if you pipe logs/alerts into a Slack channel, you can actually get really far without needing a "proper" orchestration layer. I recently took over an Airflow system from a former colleague, and in our case, it’s just overly complex for what’s really a pretty simple data flow.
But isn’t it just also python with cron?
Re: Ask HN: What is the simplest data orchestration tool you've worked with?
#30I used to work for an automation company that produced a product called ActiveBatch. It was such an amazing tool for just drag and drop automation. Its focus was on full fledged workflow automation and not just data orchestration. What I loved was its simplicity + its out of the box features. To set it up just took a simple MS SQL DB + An Installer. Bam you are up and running an absolute rock solid scheduler(i've see…
Mind you, it might have been just culture at that place, but I don't think this is as good of an example as you make it be. Sure, it was easy to get started and made the life easier at the beginning, but running it at scale was not in any way easy.