Data Access · interview question
What is the healthiest performance judgment around repository boundaries?
Multiple choiceHardchapter-11-curatedpremiumdata-accessrepository-boundaries
class OrderRepository:
def by_id(self, order_id: str) -> tuple | None:
return connection.execute("SELECT id FROM orders WHERE id = ?", (order_id,)).fetchone()Answer and explanation
Correct answer
B. Measure before optimizing, then change the part that actually dominates cost instead of guessing from style alone.
Why
Premature optimization is usually weaker than targeted optimization backed by measurement.
Test yourself on Data Access
A free test with instant, explained results. No account needed.
More Data Access questions
- What assumption should be made explicit when working with transactions?
- Which response shows the healthiest evidence-first mindset around repository boundaries?
- What production risk should you worry about most if transactions is handled lazily?
- A senior interviewer asks for one tradeoff behind transactions. What is the strongest follow-up?
- What do interviewers usually hear as a strong signal when you discuss transactions well?
- What assumption should be made explicit when working with basic sqlite queries?