Service Design · interview question
A teammate submits shaky service layer code. Which review comment is the strongest?
Multiple choiceMediumchapter-13-curatedpremiumservice-designservice-layer
Answer and explanation
Correct answer
A. Make the rule clearer and easier to explain. Place business orchestration where it can be tested and explained without the web stack attached.
Why
The best review comment anchors the change to readability, correctness, and future maintenance. If workflow decisions live in the route handler, the boundary and policy concerns collapse together.
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?