Tune caching
Cache rules and invalidation rules are peers in Airbrx — both expressed against the same attributes (user × tenant × statement × method), both authored in the same rules workshop. Fine-grained on both halves is the rare combo. These three pages cover the work.
Cache rule cookbook
Recipes grouped by intent: per-user isolation, freshness, no-PII, hot-table acceleration.
Invalidation strategies
DML-triggered, marker-driven, and TTL-only — when to reach for each, and how to combine them safely.
Handle rule issues
What the rules analyzer is telling you — shadowed rules, unreachable conditions, missing invalidation linkage.
Where caching is tuned
The App's rules workshop is where rules are authored, the API is where they're stored, and the Gateway is where they execute. You can ignore the API surface entirely if you author rules in the App; you'll reach for it when you're scripting bulk changes or generating rules from external systems.
If you're brand new to rules
Read Rules as the differentiator for the concept, then walk Ship your first cache rule for a worked end-to-end example. The pages here assume you've already shipped at least one rule.
Open the rules workshop
Authoring happens in the App. Walk the recipes below and write rules as you go.
Open in the App