Deploying to the Edge: Lessons from Cloudflare Pages

{"type":"doc","content":[{"type":"paragraph","content":[{"type":"text","text":"Running your app on the edge sounds complicated but in practice the main adjustment is learning which Node.js APIs are not available. Cloudflare Workers run on the V8 isolate runtime, not Node. Most of what you need is there — fetch, crypto, streams — but some packages assume Node internals that simply do not exist."}]},{"type":"paragraph","content":[{"type":"text","text":"The biggest surprise for most developers is the CPU time limit. Workers get a short CPU budget per request. Long-running synchronous operations will hit that limit and fail. The fix is usually to break work into smaller steps or to move it off the critical path entirely."}]},{"type":"paragraph","content":[{"type":"text","text":"Cold starts on Cloudflare Pages are fast enough that you will not notice them in practice. Isolates spin up in milliseconds, not seconds, and they stay warm as long as traffic is consistent. For a personal blog the traffic pattern is irregular, but even so the latency stays low."}]},{"type":"paragraph","content":[{"type":"text","text":"The deployment workflow is the part that works best. Push to main, watch the GitHub Actions run complete, and the new version is live globally within a minute. There is no region to pick, no deployment ring to configure, and no rollback procedure more complex than reverting a commit."}]}]}