The fact that it can be set up as an independent app or as a library is really useful.
I would also like to point out Journey ( GitHub - shipworthy/journey: Durable Workflows in a[n Elixir] package. · GitHub )
infinityfye
marciok
lawik
Nerves Core Team
Been interested in something like this. The real killer is the integrations. I did poke at some LLMs to figure out if we could run the existing Python Airflow integrations in a Port or similar and do the stuff we want in Elixir. Just as a solution to bootstrapping serious integration support.
1
lawik
Nerves Core Team
shout about it when it happens, I wanr to try it. No spare cycles or clients in that area unfortunately 
1
ghannam80
From a workflow implementation perspective, most real-world use cases require API-level integration with multiple systems to avoid forcing users to switch between different interfaces while completing a single task.
This typically includes API services , human-in-the-loop steps, event-driven triggers, and webhook-based callbacks. With that in mind, I wanted to understand whether the current approach is to handle these integrations directly within the workflow step logic, or whether there is an intention to adopt a standard communication or integration pattern to support these interactions more consistently.
1
niles
marciok
marciok
Update: Gust can be deployed in a multi-node architecture 
https://github.com/marciok/gust?tab=readme-ov-file#multi-node
3
