Përveç cache-aside bazik, ekzistojnë disa strategji caching — cache-aside, write-through, write-behind, read-through — secila me trade-off të ndryshëm të konsistencës dhe performancës. Të kuptuarit e tyre (dhe politikat e eviction) ju ndihmon të dizajnoni cache-in efektiv.
Cache-aside (lazy loading — më i zakonshëm)
App checks cache → miss → load from DB → populate cache → return.
✓ Only requested data is cached (efficient); resilient (works if cache is down)
✗ First request is a miss (slower); cache can be stale until TTL/invalidation
→ The default, most common strategy.
Write-through dhe write-behind
WRITE-THROUGH → write to cache AND DB together (synchronously) on every write
✓ Cache always fresh/consistent ✗ Writes are slower (two writes); caches unread data
WRITE-BEHIND (write-back) → write to cache immediately, write to DB ASYNC later
✓ Fast writes ✗ Risk of data loss if cache fails before the DB write; more complex
