Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

Using queues in atomic, transactional way was a core principle for building https://pgflow.dev - having whole workflow state transactionally updated alongside the work on the in db queue really simplifies a lot of things: debugging is easier, audit log is easy, reporting, stats etc are one SQL query away.


Looks interesting- but why the Supabase dependency? That’s a much tighter requirement than a vanilla PostgreSQL extension or something like PostgREST


Valid point!

So pgflow is really agnostic and Postgres is it's fundamental dependency. All components are modular and ready to be adapted to other runtimes.

It's just that Supabase is what I use and I figured out this will be my first platform, but the abstraction to port to others is there!


Nice! I'm also using queues as part of a workflow engine.


Oh really? Would love to check it out and borrow some ideas! :)




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: