S05Spring request to databaseimplemented
Repository shape, transaction boundary, and connection lifetime
Complete three independent PostgreSQL missions: query shape, proxy-owned transaction boundaries, and the connection/lock lifetime created by slow work placement.
REAL_HIBERNATE_POSTGRESQLREAL_HIKARI_POSTGRESQLPOST_FAILURE_ROWSPG_BLOCKING_PIDSNOT_OBSERVEDabout 120 min
Outcomes
- • Compare N+1 repair strategies from real Hibernate receipts.
- • Explain why a transaction boundary changes post-failure rows.
- • Separate Hikari acquisition pressure from PostgreSQL lock waiting and defend a bounded repair.
- • Keep physical query-plan and production-capacity claims outside this chapter.
Recommended context
- • s04-web-boundary
Endpoint family / fixed variants
- • /api/labs/n-plus-1
- • /api/labs/transaction-proxy
- • /api/labs/persistence-lifetime
Loading chapter experience…
Persistence available.