backend/cache_service.py: Cache key collisions possible due to lack of distinct namespacing #440

Where

backend/cache_service.py

Issue

Cache key collisions possible due to lack of distinct namespacing

Proposed Fix

Implement a prefixing system for cache keys (e.g., user:123:profile, book:45:metadata)

Why This Matters

Prevents different parts of the application from accidentally overwriting each other's cached data

I would like to work on this issue.

@devanshi14malhotra /assign