DBOS @dbos.dev · Apr 28 When workflow state is scattered across queues, caches, and databases, it becomes difficult to trace failures and recover when outages occur, whether it's due to downstream service outages, software bugs, or dependency failures. Instead, store workflows directly as Postgres rows. 🧵
1 likes 1 replies
?
Replies
2/ Database rows are easy to query and manipulate. When workflows are stored in Postgres, you can quickly see which workflows failed, why they failed, and programmatically recover them without needing a complex manual process.