Storage sync

Why you need it

Application databases still exist. Teams want Durable Execution state to land in systems they already query (warehouses, OLTP, object stores).

Code examples

Choose an SDK (preference is sticky in this browser; default Python).

# Prefer explicit application writes from Steps when you need OLTP rows.
# Keep Attributes for execution state.

Today, treat Attributes and your own application writes as the source of truth inside Flows. Export patterns vary by deployment.

How Dex implements it

Dex persists Flow Attributes and history via its Temporal/Cadence backend and blob store. First-class sync connectors to arbitrary warehouses are a platform direction (see marketing site); OSS Dex does not invent fake sync APIs in the SDKs.

Traditional workarounds

Teams build ETL from event logs, dual-writes, or CDC — each with consistency headaches.