Supabase Reviews

Temporal Reviews

Supabase mentions (554)

• Opus vs GPT on Real Ops, Part 2: One Drove, One Was Driven

  Opus, zero nudges. Realised on its own that an abandoned signup never fires identify, triangulated the anonymous session from time, platform and registration events, decoded the PostHog replay blobs, confirmed the duplicate account in Supabase, proved the reset email never sent, and pulled the root cause out of an unmasked DOM field. One prompt in; root cause out. - Source: dev.to / 21 days ago

• Supabase basics with Node.js

  Supabase is an open-source backend platform built around managed PostgreSQL. You get a database, auto-generated REST APIs (via PostgREST), Auth, file Storage, Realtime subscriptions, and Edge Functions - with a dashboard and SQL editor on top. - Source: dev.to / about 2 months ago

• How to Auto-Provision API Keys for Your Users on Sign Up with Supabase and Zuplo

  If you’re starting fresh, go to Supabase and create a new project. Once your project is ready, copy the project URL and publishable (anon) key from the project settings. - Source: dev.to / 2 months ago

• Can a Marketer Vibe-Code a Working App? 6 Lessons From My First Build

  So I had to discover that and fix that, and start leaning on our database (Supabase is what Lovable uses by default). - Source: dev.to / 2 months ago

• How I Run 3 Production AI SaaS on $5/Month of Hosting

  Verdict: start with Supabase on day one. Free tier carries you through launch. Upgrade to Pro when you legitimately outgrow it. - Source: dev.to / 2 months ago

Temporal mentions (17)

• Temporal in Production: Sharp Edges & Good Practices

  When a team moves from a monolith into microservices and event-driven, asynchronous systems, it inherits a class of problems that used to be someone else's: work that fails halfway through, steps that must not run twice, calls that return before the work is done. Temporal is a durable execution engine that handles a lot of this - you define a multi-step process, and it guarantees the process runs to completion... - Source: dev.to / 7 days ago

• Your Agent Bills While It Waits. Here's the Fix.

  Durable execution — the pattern implemented by Temporal, Inngest, Rivet Actors, and now Cloudflare Workflows — treats waiting as a continuation rather than a loop:. - Source: dev.to / 13 days ago

• Compiler as Custodian

  Two specific moves stand out in Duncan's account. The first is durable execution, via Temporal — Mercury replaced fragile cron-and-database state machines with workflow code whose failure semantics are platform-handled (replay, retry, timeout, cancellation). Mercury open-sourced its hs-temporal-sdk, which wraps Temporal's official Rust Core SDK via FFI and provides a Haskell-native API. The dovetail with Haskell's... - Source: dev.to / about 1 month ago

• How we turned our workflow editor into a real SDK

  We picked Temporal as the first reference engine on purpose. Temporal has the strictest execution model we know of – a V8 sandbox, determinism constraints, replay-driven recovery. If our port contract holds up against that, easier engines – an in-memory test double, a BullMQ queue, or JSON-first platforms like Inngest or Restate – plug in through the same two interfaces. We're shipping Temporal first; the rest is... - Source: dev.to / 2 months ago

• Three days debugging a missing trace

  The trick is to find whatever metadata channel the queue already gives you and use that and thankfully, almost every mature queue has one (probably because of this scenario). SQS has message attributes, Temporal has context propagators built into the SDK, and Hatchet (which we use to run our workflows) has a metadata field called additionalMetadata. - Source: dev.to / 4 months ago