Service Design · interview question
A teammate submits shaky repository boundaries code. Which review comment is the strongest?
Multiple choiceHardchapter-13-curatedpremiumservice-designrepository-boundaries
Answer and explanation
Correct answer
C. Make the rule clearer and easier to explain. Let the service coordinate workflow while the repository handles data access contracts and queries.
Why
The best review comment anchors the change to readability, correctness, and future maintenance. Leaking database detail into handlers or domain logic makes every change ripple farther than necessary.
Test yourself on Service Design
A free test with instant, explained results. No account needed.
More Service Design questions
- When is dependency injection being used in the wrong way?
- When is service layer being used in the wrong way?
- Which response shows the healthiest evidence-first mindset around dto mapping?
- Which option treats integration client shape as an engineering policy decision instead of a syntax trick?
- What is the clearest sign that code around integration client shape should be refactored?
- Another engineer will maintain this code later. What choice helps the most around service layer?