THE SHORT ANSWER
Caching hides the latency of bad queries but introduces stale data and eventual consistency nightmares.
Flashcards
Q1
What happens during an N+1 query problem?
An ORM executes one query to fetch N items, then N separate queries to fetch related data, destroying performance.
Q2
Why are missing indexes catastrophic under load?
The database is forced to perform full table scans for every query, consuming all available CPU and disk I/O.
Q3
When is eventual consistency the wrong choice?
When dealing with financial transactions or user states where reading stale data breaks the core business logic.
Related Concepts
Chaos Stack Field Notes FAQs
What are Chaos Stack Field Notes?
Chaos Stack Field Notes are technical flashcards that explain core engineering concepts quickly.
How are these different from topics?
Topics are broad thematic hubs that connect characters, episodes, and environments. Field Notes are short, direct Q&A flashcards for quick technical alignment.
AI Summary
This page covers Database Integrity & Query Performance as a technical flashcard. Description: Why can't caching solve bad database design?.