Foundation · retrieval review
Can you rebuild the first-request story?
Close the earlier pages. Answer aloud or on paper before opening the answer structures.
Attempt first
- A teammate says Spring Boot is “just a faster way to make controllers.” Correct that claim in two sentences, naming the responsibility it takes off your team and one responsibility it does not.
- Put validation, a business rule, and database access into their likely layers. What coupling appears if the controller owns all three?
- Predict the complete trip of
GET /tasks/42from a client typing the URL to the response body. Where would a wrong port fail differently from a wrong path? - A new endpoint returns 404 although the application starts. List the first three checks, in order, that distinguish a mapping error from a request error.
- Transfer the model: why is injecting a service into a controller easier to change than constructing it with
new?
Completion evidence
Write your request path from memory, then run one endpoint and annotate the actual status code and response. Mark Applied only after you can explain one mismatch you found.
Current status: Not started
Open answer structures after your attempt
Start with Spring Boot’s convention and auto-configuration, then trace client → host/port → server → mapping → controller → service → response. Separate failures by layer: connection/port, route/method, then application behavior. Constructor injection keeps the controller focused on HTTP translation and leaves the dependency replaceable in tests.