Quick architecture question For those running Supabase in production, how are you handling background jobs + retry logic? Just Edge Functions + pg_cron? Or something more structured? I’ve been rebuilding retry/logging logic across projects and wondering if there’s a pattern people recommend
samvms is seeking advice on handling background jobs and retry logic in Supabase production environments. They are considering using Edge Functions and pg_cron but are open to other suggestions. garyaustin suggests looking into Supabase's queues section and a user-developed tool called pgflow.
Have you looked and the queues section? https://supabase.com/docs/guides/queues
There is also this developed by a user... https://www.pgflow.dev/