Locality guarantees protect regulated data while constrained failover can reduce application availability.
Application developers need geographic confidence for stateful processing, and they also need a clear view of the resilience they give up.
Who you’d be doing this for
“Our compliance lead keeps asking where state goes during a regional failure, and I don't have a testable answer.”
Ploy Wattana · Staff Application Engineer
Builds a regulated customer portal that is moving session and workflow state to Durable Objects.
What is at stake
Developers moving regulated state to Durable Objects lack a testable way to constrain failover geography. You have to weigh strong locality controls against the availability customers surrender during regional impairment.
Why it isn’t already fixed
Every obvious fix costs something else. That’s the part you’d have to decide.
- data locality vs. regional availability
- strong guarantees vs. usable configuration
- self-service control vs. narrow policy rollout
- normal-path latency vs. failure-path evidence
Why Cloudflare
Workers and Durable Objects combine edge execution with stateful application behavior across a globally distributed network.
Written with these in mind
Not your kind of problem? 51 more at Cloudflare, or browse every organization.
This is the setup. The work is inside.
Running it puts you in the room: the full situation and its constraints, stakeholders who push back in their own words, and the decisions that are yours to make. What you produce becomes a Day One Plan — work you can show someone instead of describing.