9 ms·

Hey Kiwi, any chance of getting temporal.io style features for supabase edge functions? would love to have a one-stop-shop solution for all my real and not-real

• kiwicopple 4y ago
  (I'm assuming you want a queue/workflow engine) Temporal has done an incredible job of ensuring there will be no side-effects (even with external systems), so I doubt we'll be able to do something as extensive as they have. That said, we will probably build a simple Postgres queue/workflow engine (similar to pgboss[0]). It will live in the Postgres database (as an extension), but will be nicely integrated with Edge Functions. We haven't started this yet, so I don't have any timelines. [0] pgboss: https://github.com/timgit/pg-boss https://github.com/timgit/pg-boss
  • joisig 4y ago
    Take a look at Oban, it very well might fit the bill. https://github.com/sorentwo/oban https://github.com/sorentwo/oban
    • kiwicopple 4y ago
      we used Oban for a very early product (which we put on ice) called Supabase Workflows: https://supabase.com/blog/supabase-workflows https://supabase.com/blog/supabase-workflows The reason we paused it was the realisation that it's far more powerful to co-locate this sort of product with the data. In this case, Workflows would be more powerful as a Postgres extension - you can store the workflows into your database, create them using SQL, and the workflows would have direct access to your operational data. We'll probably re-write this using pgx[0] at some stage (if anyone is reading this and wants to attempt this, please reach out). [0] pgx: https://github.com/tcdi/pgx https://github.com/tcdi/pgx
• swyx 4y ago
  have you tried Azure Durable Functions? just curious if youve evaluated all the durable workflow solutions out there and what you came away with