Everything tagged architecture

18 published articles · newest first · server-rendered

Also filed under: cloudflare 10 · cloudflare-os 9 · mcp 5 · oip 5 · tooling 5 · durable-objects 3 · agents 2 · d1 2 · security 2 · tool-search 2 · access 1 · authentication 1 · cache 1 · canonical 1

1. The site as a folder you can hold: what the portable content graph actually measured
2. The OIP Federation Inbox Verifies Signed Agent Messages and Runs Only Audience-Bound Invokes
3. The Total Structure: Ten Books Across Three Planes — the complete OIP corpus and its architecture
4. Cloudflare OS: An LLM Operating System Built on One Account, One Deployment, One Grammar
   One AI infrastructure primitive — an ability is a database row a model reads at call time, not a definition in its prompt — and the complete feature inventory it produced: 73 systems, 879 abilities, 2
5. Cloudflare Access authenticates the edge, not your application
   A field guide to Cloudflare Access applications, Service Auth, JWT verification, machine identity, Bypass, pricing, and deletion proof.
6. Cloudflare email is three products, not one mail stack
   A practical guide to Email Routing, Email Workers, and Email Service: DNS, MIME parsing, R2 attachments, outbound limits, deliverability, costs, and the ESP boundary.
7. waitUntil, Queues, Workflows or Cron: choose by durability
   A complete Cloudflare async-work guide: guarantees, retries, poison messages, local failures, costs, runnable code and fresh Queue and Cron receipts.
8. One missing alarm guard turned a $5.75 workload into $34,895
   A decision guide to Cloudflare Workers and Durable Objects, with exact alarm guards, live pricing, deployment order, and measured production latency.
9. Pages Functions compiles 224 route files into one 1.35 MB Worker
   A complete Pages Functions guide: file routing, middleware, _routes.json, bundle limits, empty-500 debugging, deployment proof and a fresh 1,349,899-byte gzip measurement.
10. R2 cuts a 10 TB delivery bill from $923 to $18.45
    Cloudflare R2 pricing, S3 arithmetic, missing versioning, exact Worker code, and measured production behavior for deciding where files belong.
11. Workers KV makes reads fast by making writes slow and consistency optional
    A complete Workers KV guide: the 60-second consistency window, $5 writes versus $0.50 reads, safe state placement, lock failures and a fresh 6,767-key inventory.
12. D1 bills rows, not queries, and serial round trips decide the architecture
    A complete D1 operating guide: hard limits, a 50,000-to-95 row-read index result, transaction boundaries, migration drift and the D1-versus-Durable-Object verdict.
13. The Cloudflare OS: one account running an entire build
    A complete map of one production Cloudflare application: every binding, the billable unit, the $5 baseline, and the failure that produced a $34,895 invoice.
14. MCP is one view of a capability table, and the view you pick costs 6.25x
    One recorded 891-capability catalogue published three ways — zero definitions, seven tools, or 856 tools — cost 6.25× more per turn through its largest surface; live wire measurements show the moving
15. Deferred tool search against a catalogue in a database: same cost today, different scaling
    Dimension-by-dimension comparison of Anthropic's deferred tool search and keeping the capability catalogue in a database behind one endpoint. On 891 capabilities both cost the same per turn — 14,109 i
16. Resolve, read, invoke, receipt: the four calls a stranger's agent makes
    The complete cold-start loop for a model that has never seen this system: four HTTP calls with real request and response, every error string, replay and repair lineage, and a measured cost of $0.00000
17. One row of SQL is the whole contract for a capability, and the 892nd took 3.1 seconds
    Every column of the directory row that defines a callable capability on this build, the four runner types with a real row of each, why secrets are named but never stored, and the verbatim POST, receip
18. Nine tool definitions reach every capability: the catalogue is a SQL table, not a prompt
    The same 891-capability catalogue measured three ways on one build: 149,187 input tokens a turn as MCP tool definitions, 14,109 with deferred tool search, 14,071 with no MCP server at all.

Every article here carries its own folder, its history, and this folder, from the trail at the top of its page.