आधारभूत cache-aside भन्दा बाहिरै, त्यहाँ धेरै caching strategies छन् — cache-aside, write-through, write-behind, read-through — हरेकको फरक फरक consistency र performance trade-offs छन्। तिनलाई बुझ्न (र eviction policies) प्रभावकारी caching डिजाइन गर्न मद्दत गर्दछ।
Cache-aside (lazy loading — सबै भन्दा सामान्य)
text
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 र write-behind
text
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