N+1 Authorization Problem
Calling a per-item authorization check in a loop to filter a list — one call per item, plus the list query itself — instead of one bulk or reverse-lookup call that returns only what's allowed.
The N+1 pattern that plagues database queries has a direct authorization equivalent: fetch N candidate items, then call the authorization check N more times to filter them. The fix is the same shape as the database fix — a single bulk or reverse-lookup call (like OpenFGA’s ListObjects) that returns the allowed set directly, instead of asking the same question N separate times.