I was wondering if this sort of a set up is possib...
# announcements
z
I was wondering if this sort of a set up is possible with
dagster
? The other two boxes represent hosts with like an agent or a “lite” version of dagster. The agent kicks off processes on the host when main dagster scheduler tells it to.
n
As in you want to implement solids in both arbitrary python and dbt?
z
Yes
n
Sure, solids can be written however you need 🙂
z
Sorry, let me rephrase. Would I basically do a
pip install dagster
on all three boxes +
pip install dagit
on one box to get this going?
Is there a write up on how one would set up what I have diagrammed there?
n
running things on multiple servers is unrelated to the language you are writing your solids in
Look at things like dagster_celery and dagster_k8s for multi-node execution options at varying levels of complexity 🙂
z
Yeah, I think we went down the wrong path for my question. It wasn’t about the language for solids, but more about a multi-node installation. I was trying to compare the complexity for implementing a multi-node installation for dagster vs some alternatives like Airflow2, etc.
n
Overall fairly similar
Celery on Kubernetes is the usual way forward 🙂
You can mix-n-match it a bit from there
z
Thanks!
n
(Dask is also supported but I hateses it and will literally never recommend it 🙂