Skip to content

Instantly share code, notes, and snippets.

View abhiknowswhy's full-sized avatar
🏠
Working from home

Guna Abhiram Bondada abhiknowswhy

🏠
Working from home
View GitHub Profile
❌ Never Cache ⚠️ Cache with Caution ✅ Safe to Cache
Passwords or authentication credentials Session tokens (short TTL, encrypted) Public content (blog posts, marketing pages)
Credit card numbers or payment details User profile data (non-sensitive fields only) Computed aggregations (analytics, summaries)
Unencrypted sensitive personal data (medical, financial, IDs) Authorization claims (short TTL, validate critical ops) Reference data (country lists, categories)
API keys and secrets Static assets (images, CSS, JS)
Your Situation Read-Write Pattern Recommended Strategy
General web app, standard CRUD High Reads, Moderate Writes Cache-Aside + LRU + Write-Around
Financial transactions Moderate Reads, High Writes Write-Through + TTL + No cache on critical data
Social media feed High Reads, Low Writes Read-Through + Refresh-Ahead + LRU
Session storage High Reads, Moderate Writes Cache-Aside + TTL (30 min)
Product catalog (rarely changes) High Reads, Low Writes Read-Through + LRU + Long TTL (24h)
Real-time analytics dashboard High Reads, High Writes Refresh-Ahead + Short TTL (30s)
CDN/Static assets High Reads, No Writes Cache-Aside + LRU + Long TTL (7d)
Gaming leaderboards High Reads, High Writes Write-Behind + LFU + Short TTL
Strategy Read Speed (Cache Hit) Read Speed (Cache Miss) Complexity Best Use Case
Cache-Aside Fast Slow (3 round trips) Low General purpose, application controls caching
Read-Through Fast Moderate (2 round trips) Medium Read-heavy apps, CDNs, social feeds
Refresh-Ahead Fast Fast (proactive refresh) High Predictable access patterns, low latency needs
Strategy Write Speed Read Speed (After Write) Data Consistency Best Use Case
Write-Through Slow Fast High Financial transactions, critical systems
Write-Back Fast Fast Risky (potential data loss) Performance-sensitive applications
Write-Around Moderate Slow High Write-heavy, infrequent reads
User Id Password Salt Hashed Value comment
John Doe password123 XyZ9mK a1bfae8c49b7c3d4f4c (hash of password123XyZ9mK) popular password
Jane Smith 123456 AbC3dE f4g5h6i7j8k9l0m1n2o (hash of 123456AbC3dE) common password
Bob Johnson bobjohn@4518 nfu9D3 d8578edf8458ce06fbc (hash of bobjohn@4518nfu9D3) rare password
attacker1 password123 jHfip9 ajfhlkjafjahgiahrei (hash of password123jHfip9) same password as John Doe, but different hash
User Id Password Hashed Value Comment
John Doe password123 ef92b778ba5c3c9d4f4c8e5f8b6c3e5d7e6f7 popular password
Jane Smith 123456 8d969eef6ecad3c29a3a629280e686cff8ca4 common password
Bob Johnson bobjohn@4518 d8578edf8458ce06fbc5bb76a58c5ca4 rare password
attacker1 password123 ef92b778ba5c3c9d4f4c8e5f8b6c3e5d7e6f7 matched hash with John Doe
attacker2 123456 8d969eef6ecad3c29a3a629280e686cff8ca4 matched hash with Jane Smith
Password Hashed Value
password123 ef92b778ba5c3c9d4f4c8e5f8b6c3e5d7e6f7
123456 8d969eef6ecad3c29a3a629280e686cff8ca4