ARCHLEXOSS

Cloudflare · Serverless

Cloudflare Workers & R2 Application

Worker entry point with DNS, WAF and response-cache capabilities, backed by R2. This diagram is written in ArchLex and passes Cloudflare provider checks.

Edit in the playgroundCloudflare diagrams as code
Cloudflare Workers & R2 Application: Worker entry point with DNS, WAF and response-cache capabilities, backed by R2Cloudflare Workers & R2 Application: Worker entry point with DNS, WAF and response-cache capabilities, backed by R2
provider cloudflare
direction LR
account cloudflare-production {
  domain: dns["app.example.com"]
  entry: workers["Application entry"]
  protection: waf["WAF policy"]
  response-cache: cache["Response caching"]
  objects: r2["Application objects"]
  domain ->|DNS record selects entry point| entry
  protection -[protects]-> entry
  response-cache -[caches]->|Eligible application responses| entry
  entry -[reads]-> objects
}

What is in this diagram.

Resources

Relationships

Boundaries

Render it yourself.

Save the source as cloudflare-standalone.arch and render it with the CLI, or ask your agent to adapt it through the ArchLex MCP server.

npx @archlex/cli render cloudflare-standalone.arch --output cloudflare-standalone.svg

All examples