How are one-to-many associations loaded by default in JPA?

When an association is loaded depends on the mapping configuration. In a flow that assembles a response after a lookup, it's important to deliberately decide when and where the associated data is pulled out.

How do you verify a lookup service?

Check that every author appears with none omitted, that each author's own book titles are grouped correctly, and that no other author's books are mixed in. The key is to verify through the point where the response is actually assembled.

Author List Lookup Service

Your task

You want to load a list of authors and show each author's name together with the titles of the books they wrote. The service looks up the authors and returns them, and outside the service (in the controller) the response is assembled by pulling each author's book titles. Complete LibraryService.findAuthors. Note: it's a one-author-to-many-books relationship. Assembling the response (pulling book titles) happens outside the service.

Ground rules

•Single instance, in-memory H2.
•A one-to-many relationship of author to books (one author writes many books).
•The service returns the authors; assembling the response (pulling out book titles) is done outside the service.

Not required

•Pagination, sorting, filtering.
•Authentication, authorization, book create/update APIs.

▶About this challenge

Complete a lookup service built on Spring Boot 3 and JPA (in-memory H2) that loads a list of authors and shows each author's name together with the titles of the books they wrote. It is a one-author-to-many-books relationship: the service returns the authors, and assembling the response (pulling out book titles) happens outside the service.

For a one-to-many association like author–books in JPA, an important topic is when and how the associated data is pulled out as you build the response after a lookup. The service layer that handles the lookup and the outer layer that assembles the response from its result are separated by a boundary. This problem is a data-access exercise in what you have to be mindful of when handling associated data across that boundary.

How are one-to-many associations loaded by default in JPA?: When an association is loaded depends on the mapping configuration. In a flow that assembles a response after a lookup, it's important to deliberately decide when and where the associated data is pulled out.
How do you verify a lookup service?: Check that every author appears with none omitted, that each author's own book titles are grouped correctly, and that no other author's books are mixed in. The key is to verify through the point where the response is actually assembled.

Author List Lookup Service

Your task

Ground rules

•Single instance, in-memory H2.
•A one-to-many relationship of author to books (one author writes many books).
•The service returns the authors; assembling the response (pulling out book titles) is done outside the service.

Not required

•Pagination, sorting, filtering.
•Authentication, authorization, book create/update APIs.

▶About this challenge

How are one-to-many associations loaded by default in JPA?: When an association is loaded depends on the mapping configuration. In a flow that assembles a response after a lookup, it's important to deliberately decide when and where the associated data is pulled out.
How do you verify a lookup service?: Check that every author appears with none omitted, that each author's own book titles are grouped correctly, and that no other author's books are mixed in. The key is to verify through the point where the response is actually assembled.