Microsoft has open-sourced pg_durable, a PostgreSQL extension that brings durable execution — crash-safe, resumable workflow logic — into the database itself.
Durable execution is the pattern behind services like Temporal and AWS Step Functions: long-running processes checkpoint their state so a crash or restart doesn't lose work mid-flight. pg_durable ports that idea into Postgres, using the database's existing transaction machinery as the checkpoint store. The extension is available on GitHub under the microsoft org and is aimed at developers who already run Postgres and would rather not bolt on another service. Microsoft hasn't announced a managed offering or tied it explicitly to Azure.
The appeal is real: keeping workflow state in the same database as your application data collapses a failure domain and gives you transactional consistency between business data and workflow state without two-phase commit gymnastics. The tradeoff is that Postgres becomes load-bearing in a new way — durable execution workloads tend to be write-heavy, which puts fresh pressure on a server most teams are already running close to capacity.
The open-source release lands while the durable execution space is getting crowded; Temporal, Restate, and cloud-native step-function services all solve similar problems at the infrastructure layer. Microsoft's bet here is that staying inside the database is worth the tradeoff — a reasonable wager, but one that will depend heavily on whether teams right-size their Postgres instances before they start treating them as workflow engines.