fix(store): Implement version cache invalidation strategy for JetStreamEventStore #130

Merged

HugoNijhuis merged 2 commits from issue-126-untitled into main 2026-01-13 18:48:02 +00:00

Conversation 4 Commits 2 Files Changed 3

+178 -1

2 Commits

Author	SHA1	Message	Date
Claude Code	fd1938672e	fix: address review feedback on cache invalidation ... - Fix cache not repopulated after invalidation: Always update cache with fresh data instead of just deleting on mismatch - Fix race condition: Hold mutex lock during entire fetch operation to prevent SaveEvent from running between fetch and cache update - Improve test: Add second GetLatestVersion call to verify cache was properly repopulated after invalidation Co-Authored-By: Claude Code <noreply@anthropic.com>	2026-01-13 01:31:03 +01:00
Claude Code	6de897ef60	fix(store): Implement version cache invalidation strategy for JetStreamEventStore ... Implements cache invalidation on GetLatestVersion when external writers modify the JetStream stream. The strategy ensures consistency in multi-store scenarios while maintaining performance for the single-writer case. Changes: - Add cache invalidation logic to GetLatestVersion() that detects stale cache - Document version cache behavior in JetStreamEventStore struct comment - Add detailed documentation in CLAUDE.md about cache invalidation strategy - Add TestJetStreamEventStore_CacheInvalidationOnExternalWrite integration test - Cache is invalidated by deleting entry, forcing fresh fetch on next check The implementation follows the acceptance criteria by: 1. Documenting the single-writer assumption in code comments 2. Implementing cache invalidation on GetLatestVersion miss 3. Adding comprehensive test for external write scenarios Closes #126 Co-Authored-By: Claude Code <noreply@anthropic.com>	2026-01-13 00:24:27 +01:00