starcoach-hackathon/zarinpal-analytics-backend
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

docs(cache): align immutable dataset namespace

Browse Source
This commit is contained in:
Amirhossein Khalili
2026-08-20 19:00:06 +03:30
parent a0e2b70cf4
commit ec625252fb
1 changed files with 1 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
docs/decisions/0011-lazy-redis-analytics-cache.md
View File

@@ -31,7 +31,7 @@ Return `429 Too Many Requests` with `Retry-After` before enqueuing work. A manua
Send SSE heartbeat events every 15 seconds. Retain run events for one hour for authorized `Last-Event-ID` replay. After replay retention expires, return/provide the current run snapshot and continue from new events rather than replaying another merchant’s or an unbounded event history.
Payment facts are immutable during the MVP, so PostgreSQL contains no cache-revision tables or invalidation triggers. Explicit dataset replacement is an administrative recovery workflow: it selects a different completed import run as the active snapshot and therefore creates a different Redis namespace. Any future live-write integration must define insert/update/delete invalidation in a separately approved specification.
Payment facts are immutable during the MVP, so PostgreSQL contains no cache-revision tables or invalidation triggers. The sole completed import run identifies the cache namespace. Dataset replacement and any future live-write integration require separately approved namespace-selection and invalidation specifications.
Redis is a private disposable cache and coordination system, not a source of truth. PostgreSQL remains authoritative. Cached values contain approved aggregates only and exclude raw rows, payer-card keys, credentials, session tokens, and cross-tenant details.