The engineering response is not irrational. The problem is that once Cloudflare tries to be global by default and stateful at the same time, the abstraction starts leaking and the developer has to learn where the leaks are.
AWS has its own complexity, but it starts stateful design with a more concrete question:
Where should this workload live?
That naturally leads to app and database colocation, VPC networking, regional replicas, and compliance by region choice. The model is infrastructure-heavy, but it is locality-explicit from the start.
Cloudflare begins with global edge simplicity, then has to add knobs to get locality back.
placement jurisdiction sessions bookmarks regional services host affinity data location
That is why the complexity feels different. It is not just infrastructure complexity. It is abstraction-reconciliation complexity.
None of this is random. If Cloudflare wants to remain only DNS, CDN, and WAF, it can stay simpler. If it wants to compete as an application cloud, it has to confront state.
More primitives More placement choices More consistency models More data locality decisions More mental overhead
The developer has to decide not only how to deploy, but also where code runs, where data lives, when consistency matters, and when edge-local execution is actually the wrong choice.
replicas leak consistency placement leaks locality jurisdictions leak compliance Durable Objects leak coordination Regional Services leak processing boundaries
Those leaks are not proof of failure. They are evidence that the platform is touching the hardest parts of distributed systems.
Cloudflare's old magic was "put us in front of your app and we make the Internet safer and faster."
The new promise is much harder: "build the app on us and we make it global by default."
That second promise inherits the hardest problem in distributed systems: state.
For stateless workloads, Cloudflare can still feel beautifully simple. For stateful workloads, the platform becomes more explicit about replicas, locality, compliance, and coordination.
That complexity is not an accident. It is the cost of ambition.
The edge becomes complicated at the exact moment it tries to become a cloud. Once state enters the picture, the developer has to pay attention to what the abstraction used to hide.