toiljs 0.0.116 → 0.0.118

package/docs/services/analytics.md

@@ -1,279 +0,0 @@
-# Analytics
-
-Read your site's own usage numbers (requests, bytes, cache hits, database ops, errors, and more) straight from a route, with no extra code and no third-party service.
-
-Reach for analytics to build a status or usage dashboard for a site: how much traffic it serves, how effective its cache is, how many database operations it runs. It is **infrastructure metering per domain**, not per-user product analytics. There are no custom events; you read a fixed catalog of counters the edge already keeps for you.
-
-`Analytics` is an **ambient global**: use it with no import, like [`crypto`](./crypto.md) or `Time`.
-
-## What "metering" means
-
-Every time the edge (the Dacely server running your code) serves a request, runs a database operation, opens a stream, or sends an email, it **counts** that into a set of per-domain counters. Those counters live in the same worldwide, distributed database that backs [ToilDB](../database/README.md), so the total for your site is correct across every edge location, not just the one machine that happened to serve a request.
-
-`Analytics.self()` reads a **snapshot** of your site's current counter values. You do not record anything yourself; the numbers are already there.
-
-```mermaid
-flowchart LR
-    R["Every request, DB op,<br/>stream, email"] --> C["Edge counts it into<br/>per-domain counters"]
-    C --> D[("Distributed counters,<br/>worldwide")]
-    D --> S["Analytics.self()<br/>reads a snapshot"]
-    S --> Y["Your route returns<br/>the numbers"]
-```
-
-## Read your site's stats
-
-`Analytics.self()` returns a `TenantStats` object. Every counter is a **named getter** that returns a `u64` (an unsigned 64-bit integer, always zero or positive), so mapping the numbers into a response needs no casts at all.
-
-```ts
-import { RouteContext } from 'toiljs/server/runtime';
-
-@rest('metrics')
-class Metrics {
-    @get('/')
-    public overview(ctx: RouteContext): string {
-        const s = Analytics.self();
-        // Every getter is a u64. cacheRatio is the one f64 (a fraction 0..1).
-        return `requests=${s.requests} cacheHits=${s.cacheHits} ratio=${s.cacheRatio}`;
-    }
-}
-```
-
-You can also read any counter by its numeric id with `s.metric(MetricId.Requests)`, which returns `0` for an unknown id. The named getters are preferred: they are self-documenting and there are no magic strings to mistype.
-
-### The counter catalog
-
-Every getter below is a lifetime running total: it only ever goes up, and reading it never resets it. They are grouped by area. (`MetricId` is the matching numeric id, an ambient enum you can use with no import.)
-
-**Requests and the L1 edge**
-
-| Getter | What it counts |
-| --- | --- |
-| `requests` | HTTP requests served |
-| `bytesOutL1` | Response bytes sent |
-| `bytesInL1` | Request bytes received |
-| `status2xx` | 2xx responses (success) |
-| `status3xx` | 3xx responses (redirects) |
-| `status4xx` | 4xx responses (client errors) |
-| `status5xx` | 5xx responses (server errors) |
-| `staticHits` | Static assets served without running your code |
-| `wasmDispatches` | Times your compiled handler ran |
-| `executorFullRejects` | Requests rejected because the worker pool was full |
-| `unknownHostRejects` | Requests rejected for an unknown host |
-| `rateLimitedRejects` | Requests rejected by rate limiting |
-| `gasUsed` | Total compute "gas" your handlers consumed |
-
-**Database (ToilDB)**
-
-| Getter | What it counts |
-| --- | --- |
-| `dbOps` | Database operations issued |
-| `dbReads` | Read operations |
-| `dbWrites` | Write operations |
-| `dbErrors` | Operations that errored |
-| `dbLatencyNsSum` | Summed operation latency, in nanoseconds |
-| `meanDbLatencyNs` | Derived: `dbLatencyNsSum / dbOps` (0 with no ops) |
-
-**Streams (WebTransport realtime)**
-
-| Getter | What it counts |
-| --- | --- |
-| `streamAccepts` | Stream connections accepted |
-| `streamRejectWrongNode` | Streams that reached the wrong node |
-| `streamRejectCapacity` | Streams rejected for capacity |
-| `streamRejectArtifact` | Streams rejected for a missing or invalid build |
-| `streamRejectGuest` | Streams your code rejected |
-| `streamTraps` | Stream handler crashes |
-| `streamIdleTimeouts` | Streams closed for being idle |
-| `streamBytesIn` / `streamBytesOut` | Bytes received / sent on streams |
-| `streamBackpressureEvents` | Times a stream had to slow down |
-| `streamCloses` | Clean closes |
-| `streamDisconnects` | Abrupt disconnects |
-
-**Daemons (L4 background jobs)**
-
-| Getter | What it counts |
-| --- | --- |
-| `daemonStarts` / `daemonStartFailures` | Daemon starts / failed starts |
-| `daemonTicksFired` | Scheduled ticks that ran |
-| `daemonTicksSkippedNotLeader` | Ticks skipped because this node was not the leader |
-| `daemonTicksFailed` | Ticks that failed |
-| `daemonLeaderAcquires` / `daemonLeaderFenced` | Leadership gained / lost |
-| `daemonHttpCallAttempts` / `daemonHttpCallFailures` | Outbound HTTP calls attempted / failed |
-
-**Memory, email, and cache**
-
-| Getter | What it counts |
-| --- | --- |
-| `memGrownBytes` | Wasm memory grown, in bytes |
-| `emails` | Emails sent |
-| `cacheHits` | Responses served from the edge cache |
-| `cacheMisses` | Cacheable responses that missed the cache |
-| `cacheRatio` | Derived **`f64`**: `cacheHits / (cacheHits + cacheMisses)`, a fraction from 0 to 1 (0 when there were no cacheable responses) |
-
-### Live gauges and request meters
-
-A few fields are not lifetime totals. They still read as `u64` (except the derived `sustainedRpsCap`, an `f64`).
-
-**Live gauges** are the current level right now, not a running total:
-
-- `connectedStreams`: streams connected at this moment.
-- `committedMemory`: wasm memory committed right now, in bytes.
-
-**Request meters** show where you sit against your plan. The model is a **sustained-rate ("unmetered pipe")** one, not a fixed per-minute ceiling. Your plan has a **sustained request rate** `X` (requests per second), measured over a **3-minute rolling window**. Two important consequences:
-
-- **Instantaneous spikes are free.** There is no per-tier cap on how fast you may burst inside a window; you may spike right up to the box's own hardware ceiling (the `firewall.global_pps` DDoS backstop, shared across all tenants). Nothing throttles you for a brief peak.
-- **Only sustained overuse throttles.** You get an HTTP `429` once your fleet-global request count over the *trailing* 3 minutes exceeds `X * 180` (the sustained rate integrated over the window), or once your 30-day quota is exhausted. "Fleet-global" means the count is summed across every edge location, not just the one machine serving you.
-
-Because the window **rolls**, a burst ages out gradually over the following 3 minutes rather than being forgiven all at once on a boundary. The `Retry-After` on a `429` tells you exactly how long until enough of it has decayed.
-
-The fields:
-
-- `reqBurstUsed` / `reqBurstCap`: fleet-global requests in the **trailing 3-minute rolling window**, and its allowance. This is exactly the number the edge compares against, so it never disagrees with why you were throttled. The allowance is `X * 180` (the window is `BURST_WINDOW_SECS = 180` seconds). A cap of `0` means **unmetered** (no sustained cap).
-- `req30dUsed` / `req30dCap`: fleet-global requests in the **current 30-day window**, and the 30-day quota. This one still tumbles, because it is a billing period rather than a rate. A quota of `0` means **unmetered**.
-- `sustainedRpsCap`: a convenience `f64` derived from the burst cap, `reqBurstCap / BURST_WINDOW_SECS`. This is your plan's sustained rate `X` in requests/second (`0.0` when unmetered), so you can show "1000 rps sustained" without doing the division yourself.
-
-There is also `nowMs`, the edge wall-clock time (in milliseconds) when the snapshot was taken, so you can show "as of" and compute how fresh the numbers are.
-
-## Time series (for graphs)
-
-The totals above are single numbers. To draw a graph over time, use `Analytics.series(metric, range)`, which returns a `Series`: a list of per-bucket totals from oldest to newest.
-
-```ts
-@get('/requests-24h')
-public requests24h(ctx: RouteContext): string {
-    const s = Analytics.series(MetricId.Requests, AnalyticsRange.H24);
-    // s.points        -> per-bucket totals, oldest to newest
-    // s.bucketSecs    -> seconds each bucket covers
-    // s.headMs        -> end time (ms) of the newest bucket
-    // s.ratePerSec(i) -> requests/second for bucket i (points[i] / bucketSecs)
-    return `buckets=${s.points.length} bucketSecs=${s.bucketSecs}`;
-}
-```
-
-`AnalyticsRange` picks the window and the resolution. Short ranges use per-minute buckets for a smooth line; the rest use per-hour buckets (kept for 30 days):
-
-| Range | Span | Bucket width |
-| --- | --- | --- |
-| `H1` | 1 hour | 1 minute |
-| `H6` | 6 hours | 1 minute |
-| `H12` | 12 hours | 1 hour |
-| `H24` | 24 hours | 1 hour |
-| `D3` | 3 days | 1 hour |
-| `D7` | 7 days | 1 hour |
-| `D14` | 14 days | 1 hour |
-| `D30` | 30 days | 1 hour |
-
-The series stores **totals per bucket**, never rates. A rate is derived: `ratePerSec(i)` divides bucket `i` by its width for you, or you can compute `points[i] / bucketSecs` yourself. Most metrics you will chart are counters (`MetricId.Requests`, `MetricId.CacheHits`, and so on).
-
-## Permissions: who can read what
-
-- **Your own site.** `Analytics.self()` and `Analytics.series(...)` always read the site the request landed on. The calling domain is decided by the edge; your code cannot forge it.
-- **Cross-site reads are for `dacely.com` only.** The privileged `dacely.com` domain (the platform dashboard) may read any site with `Analytics.site(domain)`, `Analytics.siteSeries(domain, ...)`, and `Analytics.listSites(...)`. For any other caller, or an unknown domain, `site` and `siteSeries` return `null` and `listSites` returns an empty page. There is no way for a normal site to read another site's numbers.
-
-`Analytics.listSites(cursor, limit)` enumerates site names for the dashboard, one page at a time. It returns a `SiteList` with `sites: string[]` and `hasMore: bool`. When `hasMore` is true, pass the last name back as the next `cursor` to get the following page.
-
-```ts
-// Only meaningful when the calling domain is dacely.com.
-const page = Analytics.listSites('', 100); // first 100 site names
-for (let i = 0; i < page.sites.length; i++) {
-    const other = Analytics.site(page.sites[i]); // TenantStats | null
-    if (other != null) {
-        // read other.requests, other.cacheRatio, ...
-    }
-}
-```
-
-## Worked example: return everything
-
-This route reads the full snapshot and maps it into a typed response. Mapping is mechanical: nearly every getter is a `u64` and maps to a `u64` field with no cast; the only `f64` values are the derived `cacheRatio` and `sustainedRpsCap`. The example groups a representative field from each area; add the rest of the getters from the catalog above the same way.
-
-```ts
-import { RouteContext } from 'toiljs/server/runtime';
-
-/** The shape returned to the client. All fields are u64 except the two derived f64s (cacheRatio, sustainedRpsCap). */
-@data
-export class UsageReport {
-    // requests / L1
-    requests: u64 = 0;
-    bytesOut: u64 = 0;
-    status2xx: u64 = 0;
-    status5xx: u64 = 0;
-    gasUsed: u64 = 0;
-    // database
-    dbOps: u64 = 0;
-    dbErrors: u64 = 0;
-    meanDbLatencyNs: u64 = 0;
-    // cache
-    cacheHits: u64 = 0;
-    cacheMisses: u64 = 0;
-    cacheRatio: f64 = 0;
-    // live gauges (current level, not a total)
-    connectedStreams: u64 = 0;
-    committedMemory: u64 = 0;
-    // request meters (cap 0 = unmetered)
-    reqBurstUsed: u64 = 0;   // requests in the current 3-minute sustained-rate bucket
-    reqBurstCap: u64 = 0;    // per-bucket cap = sustained_rps * 180
-    req30dUsed: u64 = 0;     // requests in the current 30-day window
-    req30dCap: u64 = 0;      // 30-day quota
-    sustainedRpsCap: f64 = 0; // derived: reqBurstCap / 180 (the plan's sustained rps)
-    // when the snapshot was read (edge ms)
-    nowMs: u64 = 0;
-}
-
-@rest('usage')
-class Usage {
-    @get('/')
-    public report(ctx: RouteContext): UsageReport {
-        const s = Analytics.self();
-        const out = new UsageReport();
-
-        out.requests = s.requests;
-        out.bytesOut = s.bytesOutL1;
-        out.status2xx = s.status2xx;
-        out.status5xx = s.status5xx;
-        out.gasUsed = s.gasUsed;
-
-        out.dbOps = s.dbOps;
-        out.dbErrors = s.dbErrors;
-        out.meanDbLatencyNs = s.meanDbLatencyNs;
-
-        out.cacheHits = s.cacheHits;
-        out.cacheMisses = s.cacheMisses;
-        out.cacheRatio = s.cacheRatio;
-
-        out.connectedStreams = s.connectedStreams;
-        out.committedMemory = s.committedMemory;
-
-        out.reqBurstUsed = s.reqBurstUsed;
-        out.reqBurstCap = s.reqBurstCap;
-        out.req30dUsed = s.req30dUsed;
-        out.req30dCap = s.req30dCap;
-        out.sustainedRpsCap = s.sustainedRpsCap;
-
-        out.nowMs = s.nowMs;
-        return out;
-    }
-}
-```
-
-Because this is a `@data` return type, the client gets a fully typed result from `Server.REST.usage.report()`. See [structured data types](../backend/data.md) for how `@data` works.
-
-## Local dev behavior
-
-Under `toiljs dev`, the real per-domain metering does not exist (there is only one machine and no fleet), so the dev server returns a **fixed sample** `TenantStats` and a gentle synthetic ramp for `series(...)`. That lets you build and style a dashboard locally. Dev is also permissive: it returns sample data for any domain, because the real `dacely.com`-only check is enforced on the edge. Your code is unchanged; only the numbers differ.
-
-## Gotchas and limits
-
-- **Totals never reset.** The counter getters are lifetime running totals. To see "requests in the last hour", use `series(...)` and sum the buckets, not the totals.
-- **Values are `u64`.** Map them into `u64` fields with no casts. The non-integer fields are `cacheRatio` and `sustainedRpsCap` (and `Series.ratePerSec`), which are `f64`.
-- **Spikes are free; only sustained overuse throttles.** The request meters follow a sustained-rate model: you may burst up to the box's hardware ceiling, and throttling (`429`) starts only when the current 3-minute bucket passes `sustainedRpsCap * 180`, or when the 30-day quota runs out. A cap or quota of `0` means unmetered.
-- **Not per-user analytics.** These are infrastructure counters per domain. There is no way to record a custom event or attribute a number to a specific user.
-- **Cross-site reads need `dacely.com`.** `Analytics.site(...)` returns `null` for everyone else. Do not build a feature that reads another site's stats.
-- **Snapshots, not live streams.** Each call reads the current values once. `nowMs` tells you when.
-
-## Related
-
-- [Caching](./caching.md), the source of `cacheHits`, `cacheMisses`, and `cacheRatio`.
-- [ToilDB database](../database/README.md), the source of the `db*` counters and where these counters are stored.
-- [Structured data types](../backend/data.md), for the `@data` return type in the worked example.
-- [Compute tiers](../concepts/tiers.md), for what "L1", "streams", and "daemons" mean in the catalog.

package/docs/services/caching.md

@@ -1,175 +0,0 @@
-# Caching
-
-**Caching lets the edge keep a copy of a response and hand it back instantly, without re-running your code.** You opt in per route, either with the `@cache` decorator or by calling `Response.cache(...)`.
-
-## What "cache" means here
-
-A **cache** is a fast, temporary store of a previous answer. When a request comes in, the edge can check: "have I already computed this exact response recently?" If yes, that is a **cache hit**: it returns the saved copy in microseconds and never wakes up your WebAssembly program. If no, that is a **cache miss**: it runs your handler, sends the result, and (if you asked it to) saves a copy for next time.
-
-There are two places a response can be cached:
-
-- **The edge cache** is shared: one saved copy on an edge server answers many users. This is where the big speedups come from.
-- **The browser cache** is private to one user's browser. You control it with a standard `Cache-Control` header.
-
-You can use one or both.
-
-## When to cache (and when not)
-
-Cache a response only when it is the **same for everyone** and safe to reuse for a little while:
-
-- Good: a public leaderboard, a product catalog, a blog index, an exchange-rate snapshot, a "server status" endpoint.
-- Bad: anything personalized (a user's dashboard, their cart, "hello, Alice"). If you cached that, one user could be served another user's data. The edge has strong safety rails against this (below), but the simplest rule is: **do not cache per-user data on the shared edge.**
-
-Caching is **always opt-in**. A response you do not mark is never stored. There is no "cache every GET" mode, because the edge cannot tell a personalized response from a public one on its own.
-
-## How: the `@cache` decorator
-
-A **decorator** is an annotation you put right above a route method. `@cache` tells the edge how long it may reuse the response. The numbers are positional:
-
-```ts
-import { Response } from 'toiljs/server/runtime';
-
-@rest('leaderboard')
-class Leaderboard {
-    @cache(60)                    // 60 MINUTES at the edge
-    @get('/')
-    public top(): Response {
-        // ...expensive query...
-        return Response.json(standings);
-    }
-}
-```
-
-The full form is `@cache(edgeTtlMinutes, browserTtlSeconds?, privateScope?, allowAuth?)`:
-
-```ts
-@cache(60)                  // 60 minutes at the edge, browser does not cache
-@cache(60, 300)             // + tell the browser to cache for 5 minutes (300s)
-@cache(60, 300, true)       // + mark it "private": browser only, never the shared edge
-@cache(60, 300, true, true) // + allow caching even for logged-in requests (see rails)
-```
-
-**TTL** means "time to live": how long a saved copy stays fresh before the edge throws it away and recomputes. Notice the units differ on purpose: the edge TTL is in **minutes**, the browser TTL is in **seconds**.
-
-Every argument must be a plain number or `true`/`false` literal. If you pass something computed (a variable, a function call), the decorator safely degrades to "not cached" instead of misbehaving.
-
-## How: `Response.cache(...)`
-
-`@cache` is just a shorthand. You can do the same thing by hand on any `Response`, which is handy when you decide at runtime:
-
-```ts
-public cache(
-    edgeTtlMinutes: u16,
-    browserTtlSeconds: u32 = 0,
-    privateScope: bool = false,
-    allowAuth: bool = false,
-): Response
-```
-
-```ts
-return Response.json(body).cache(60, 300);
-```
-
-`cache(...)` returns the same `Response`, so it chains. There is also a shorthand for "edge only, no browser caching":
-
-```ts
-return Response.bytes(blob).cacheFor(5); // edge-cache 5 minutes
-```
-
-Under the hood, both set one header, `Dacely-Cache-Control`, that the edge reads and then strips (it never reaches the client).
-
-## The parameters, in detail
-
-| Parameter | What it does |
-| --- | --- |
-| `edgeTtlMinutes` | How long the shared edge may serve the saved copy. Clamped to a 24-hour maximum, no matter what you pass. `0` means no edge caching. |
-| `browserTtlSeconds` | The `max-age` sent to the browser. `0` (default) means the browser is told not to cache. |
-| `privateScope` | Marks the response `private`: it may only live in the browser's own cache, never the shared edge or a CDN. |
-| `allowAuth` | Permits caching a response to a logged-in request. Off by default (see safety rails). |
-
-## A hit vs a miss, visually
-
-```mermaid
-flowchart TD
-    R["Request arrives<br/>at the edge"] --> Q{"Saved copy<br/>still fresh?"}
-    Q -->|Yes: cache HIT| H["Return the saved response<br/>(microseconds, no code runs)"]
-    Q -->|No: cache MISS| M["Run your WebAssembly handler"]
-    M --> D{"Marked cacheable<br/>and eligible?"}
-    D -->|Yes| S["Save a copy for the TTL,<br/>then return it"]
-    D -->|No| X["Return it, save nothing"]
-```
-
-Every response the edge sends carries a `Dacely-Cache` header so you can see what happened while debugging:
-
-| `Dacely-Cache` value | Meaning |
-| --- | --- |
-| `HIT` | Served from the cache; your code did not run. |
-| `MISS` | Your code ran, and the response was saved (the next identical request should `HIT`). |
-| `DYNAMIC` | Your code ran, and the response was not cached (no directive, or not eligible). |
-| `BYPASS` | A fallback path (for example the compute layer was momentarily unavailable); not a cached answer. |
-
-## Safety rails (why cross-user leaks cannot happen)
-
-The edge refuses to store certain responses even if you asked it to. These rules exist because a shared cache is exactly where one user's data could accidentally leak to another:
-
-- **5xx responses are never cached.** A server error is temporary; caching a `500` would keep serving the failure for the whole TTL. (2xx, 3xx, and 4xx are cacheable: a redirect or a `404`/`410` is a predictable function of the request.)
-- **A response with a `Set-Cookie` is never cached.** A cookie is per-user state.
-- **A response to a logged-in request is not cached** unless you pass `allowAuth = true`. This stops one user's personalized response from being handed to someone else. Even with `allowAuth = true`, such an entry is only ever served back to other **authenticated** requests, never to an anonymous one (which would skip the auth check entirely).
-- **The edge TTL is clamped to 24 hours.**
-
-The cache is also keyed precisely: an entry is identified by the **host, method, path, and the exact request body**. So a `POST` with body `A` never returns the copy saved for body `B`, and a `GET` never returns a `POST`'s copy.
-
-Because auth checks and body decoding run **before** the cache directive is applied, an unauthorized request is rejected with `401` before anything is stored, and a cached copy only ever comes from a handler that actually ran successfully.
-
-## ETag, Last-Modified, and 304 (static files)
-
-The `@cache` decorator above is for **dynamic** responses (ones your code computes). Your project's **static files** (the built HTML, JS, CSS, and images) get a second, automatic layer of caching that you do not configure. It is worth understanding because it is what makes repeat page loads cheap.
-
-Every static file the edge serves carries three headers:
-
-- **`ETag`**: a short fingerprint of the file's contents (a "version tag"). toiljs uses a *weak* ETag (it starts with `W/`), which survives compression by a CDN in front of the edge.
-- **`Last-Modified`**: when the file last changed.
-- **`Cache-Control`**: content-hashed assets (files whose name contains their content hash, like `app-CfvHW67Y.js`) get `immutable` with a one-year max-age, because the URL itself changes whenever the content does. Everything else (HTML, non-hashed assets) gets `must-revalidate`, so the browser always checks freshness.
-
-**Revalidation** is the trick. Instead of re-downloading a file it already has, a browser asks "has this changed?" by echoing the tag back in an `If-None-Match` header (or the date in `If-Modified-Since`). If the file is unchanged, the edge replies **`304 Not Modified`** with an empty body, and the browser reuses its copy. A `304` is tiny and fast.
-
-```mermaid
-sequenceDiagram
-    participant B as Browser
-    participant E as Dacely edge
-    B->>E: GET /app.js<br/>If-None-Match: W/"1a2b-c3d4"
-    alt file unchanged
-        E-->>B: 304 Not Modified<br/>(no body)
-    else file changed
-        E-->>B: 200 OK<br/>(new bytes + new ETag)
-    end
-```
-
-The precedence follows the HTTP spec (RFC 7232): if the request has `If-None-Match`, that decides it; only when it is absent does `If-Modified-Since` apply. You get all of this for free; there is nothing to turn on.
-
-## Where cached bodies live (memory bounds)
-
-You do not need this to use caching, but it explains the limits you may hit.
-
-The edge response cache is bounded and hard-capped so it can never exhaust a node's memory:
-
-- **RAM tier**: small, short-lived responses live in memory, within a bounded budget (on the order of ~128 MB) plus a cap on the number of entries. A single response over ~256 KB does not go in RAM.
-- **Disk tier (optional)**: when the operator enables an on-disk spill directory, a **big** response (over ~256 KB) or a **long-lived** one (TTL of 10 minutes or more) is written to disk and served back with near-zero RAM, the same way static files are. If disk spill is not enabled, a big response is simply not cached (you will see `Dacely-Cache: DYNAMIC`).
-
-Expired entries are dropped on read (a stale entry is treated as a miss) and reclaimed when the cache needs room. Nothing survives a process restart.
-
-## Gotchas
-
-- **Units differ.** Edge TTL is in minutes; browser TTL is in seconds. `@cache(60)` is one hour at the edge, not one minute.
-- **Do not cache personalized data on the shared edge.** If a response depends on who is asking, either do not cache it, or use `privateScope` so it is browser-only.
-- **A `Set-Cookie` disables edge caching for that response.** If you set a cookie, that response will not be edge-cached, by design.
-- **Very large or slow-to-change bodies may not be cached** unless disk spill is enabled on the node. Check the `Dacely-Cache` header if a response you expected to cache shows `DYNAMIC`.
-- **Nothing persists across restarts.** The cache is a speed optimization, never a source of truth.
-
-## Related
-
-- [Rate limiting](./ratelimit.md): protect a route before it runs.
-- [Analytics](./analytics.md): see your cache hit ratio per site.
-- [Cookies](./cookies.md): why a `Set-Cookie` opts a response out of edge caching.
-- [Auth, sessions, and `@user`](../auth/usage.md): why logged-in responses are not cached by default.
-- [Every decorator](../concepts/decorators.md).