Caching Data

Brix has separate native data and route-edge caching systems. Use these focused guides to configure policies, invalidate changed data, and select stores without crossing cache ownership boundaries.

Native data caching reuses validated reads for executeApi, useApi, and Contentful clients. Route cache settings are only edge hints for complete responses; they do not create a Brix response store.

Choose a workflow

• Configure eligibility, scope, freshness, and fallback policies.
• Invalidate contracts or tags while preserving cache ownership boundaries.
• Select memory, DynamoDB, or Fastly KV stores and configure edge hints.