3 ms·
I've been using https://www.pgflow.dev https://www.pgflow.dev for workflows which is built on pgmq and am really impressed so far. Most of the logic is in the d
by cpursley 1y ago
I've been using https://www.pgflow.dev https://www.pgflow.dev for workflows which is built on pgmq and am really impressed so far. Most of the logic is in the database so I'm considering building an Elixir adapter DSL.
- ishita_julep 1y agowhat are you using the DSL for?
- cpursley 1y agoIt’s used to generate the database migration that defines the flows. More syntax sugar than anything.
- mmcclure 1y agoJust curious, if you’re already in Elixir and using Postgres, why not use Oban[1]? It’s my absolute favorite background job library, and the thing I often miss most when working in other ecosystems. [1] https://github.com/oban-bg/oban https://github.com/oban-bg/oban
- sbrother 1y agoOban is so good! My startup has an extensive graph of background jobs all managed by Oban, and it's just rock solid, simple to use and gets out of the way.
- cpursley 1y agoOban is awesome, but I really like the ideas around pgmq and most of the logic living in the database. And the idea of "flows" design from pgflow for multi-step processes (which Elixir is naturally a great match for)