Cloudflare Platform

Workflow

Confirm project/runtime, compatibility date, bindings, routes, deployment method and environment.
Choose primitives by consistency, access pattern, object size, coordination and delivery semantics rather than familiarity.
Keep secrets in platform secret storage and minimize public bindings/routes.
Validate migrations/bindings before production deployment.
Treat Worker versions and storage state separately: Worker version rollback does not roll back D1/KV/R2/Durable Object state.
Inspect deployment and runtime logs plus actual HTTP behavior after release.

Conditional references

Storage/coordination choice → references/platform-selection.md.
Bindings/configuration → references/bindings.md.
Deployment/rollback reasoning → references/deployments.md.

Available scripts

scripts/inspect-project.sh — read-only local project/Wrangler inventory.

Asset

Use assets/architecture-checklist.md for architecture reviews.

Guardrails

Cloudflare capabilities and limits change quickly. Re-check current official docs for limits, pricing and beta/GA status before architecture decisions.

cloudflare-platform