Example: Flashcard

Repositories use NamedParameterJdbcTemplate directly. The executed SQL is visible in the code. Inserts are the exception: SimpleJdbcInsert reads the table metadata and returns the generated key, with SimplePropertySqlParameterSource taking the values straight off the domain record. SmartDeckRepository still spells its parameters out, because its SmartCondition enum has to reach the driver as name() rather than as an enum. Row mapping goes through DataClassRowMapper; the reflection this pair needs under a native image is a config the build generates from the domain package.

No container; FlashcardContext wires everything by calling constructors directly, playing the role of Spring’s ApplicationContext by hand.

Instead of AOP, services call Transactions.write()/read(), a thin wrapper around TransactionTemplate. The wrapped block is exactly the transaction scope.

As a bonus, a JSON API (/api/decks, /api/decks/{id}/cards) sits on the same service layer to show the framework’s REST support. Its wire format is in flashcard.web.Codecs as hand-written JsonWriter/JsonReader lambdas.

/_routes lists every route and /openapi.json is the same list as an OpenAPI 3.1 document, both built from app.routes(), which is what the framework exposing its routing table as data buys you.

There is no Controller interface. FlashcardApp.registerRoutes is the whole table, and handlers arrive as an Action class, a public method reference, or a lambda.