The failure mode isn’t “using Postgres/FoundationDB as a queue” so much as…

The failure mode isn’t “using Postgres/FoundationDB as a queue” so much as asking one system to be your source of truth, scheduler, retry engine, and backpressure valve all at once. Keeping durable business state in the database is correct; letting it also handle dispatch and worker coordination invites scans, write contention, and operational cruft once agents fan out. Move scheduling and dispatch to a real queue (Kafka, managed pub/sub, etc.) before concurrency turns lock contention into an outage; treat the DB as the truth and the queue as the coordination layer.