Q1. Explain caching strategies and common failure modes.
Strategies: - Cache-aside (lazy loading): app checks cache, on miss reads DB and populates. Most common. - Read-through: cache library fetches on miss. - Write-through: w...
Technical Question Bank · Peer-Reviewed
Job Interview Questions and Answers Directory
Search and filter frequently asked interview questions across technical, programming, and behavioral domains. Tailor your interview preparation by difficulty for freshers or experienced developers (4 available).
Active:
Tag: invalidation ×
Q2. Compare write-through, write-behind and write-around caching.
- Write-through: write to the cache and the database in the same operation, synchronously. The cache stays fresh and reads are fast, but writes are slower and every write...
Q3. How do you invalidate cached data?
Invalidation is the hardest part of caching. Options, often combined: - TTL expiry: every entry has a lifetime; simple and self-healing, but data can be stale until it ex...
Q4. How do you keep a cache consistent with the database?
Perfect consistency is not achievable without giving up caching; aim for bounded staleness and correct behavior. Practical rules: - On write, commit to the database first...