Service Design · interview question

What is the healthiest performance judgment around repository boundaries?

Multiple choiceHardchapter-13-curatedpremiumservice-designrepository-boundaries

python

@app.post("/orders")
def create_order(request: CreateOrderRequest, service: OrderService = Depends(get_service)):
    return service.create(request)

Delay clarity until production traffic reveals the edge case and then patch it under pressure.Measure before optimizing, then change the part that actually dominates cost instead of guessing from style alone.Keep repository boundaries implicit so the script stays short and hope the next engineer infers the rule.Solve the symptom with comments only and avoid changing the code shape around repository boundaries.

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 Service Design

A free test with instant, explained results. No account needed.

Start free test

All Service Design questions →

What is the healthiest performance judgment around repository boundaries?

Correct answer

Why

More Service Design questions