docs(explanation): add caching chapter covering all layers#160
Merged
Conversation
Maps the full cache chain from query dict to object: query result cache, prepared statements, request connection pool, zodb-pgjsonb LoadCache, ZODB Connection object cache, PG shared_buffers. Explains the invariant that brains and getObject results are deliberately not memoized (request-boundary hygiene, ZODB handles it in the right scope), and documents prefetch, invalidation rules, and every configuration knob. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
New Diataxis Explanation chapter at `docs/sources/explanation/caching.md`.
Why
We had caching fragments scattered across `performance.md` but no consolidated page that answers "what is cached where, for how long, and how does it get invalidated" — which is exactly what a reader needs when sort/pagination looks unstable or `getObject()` appears to return stale data.
What it covers
Test plan
🤖 Generated with Claude Code