3 ms·
Very nice, Oban is great. I effectually found a similar approach with pgflow.dev (built around pgmq) - but the stateless deno "workers" are pretty unreliable an
by cpursley 8mo ago
Very nice, Oban is great. I effectually found a similar approach with pgflow.dev (built around pgmq) - but the stateless deno "workers" are pretty unreliable and built an elixir worker (https://github.com/agoodway/pgflow https://github.com/agoodway/pgflow) that can pick up and process jobs that were created by pgflow's supabase/typescript client. So maybe there's an opportunity also with Oban to have a TypeScript/Node client that can insert jobs that Elixir/Python Oban can pick up. Also, I wonder if another approach vs the python workers picking things up is to have elixir workers call/run python/lua, etc code or is that too limiting?
- elitepleb 8mo agothat's easy with https://hexdocs.pm/pythonx/Pythonx.html https://hexdocs.pm/pythonx/Pythonx.html and https://hexdocs.pm/lua/Lua.html https://hexdocs.pm/lua/Lua.html and works well too
- cpursley 8mo agobtw, a lot of postgres envs are not going to have pgmq, so just use Oban and don't reinvent the wheel like I did ;)