Choosing a persistence approach
On This Lesson 4 topics
This lesson is planned. The outline below lists the topics it will cover. The full lesson has not been published yet.
In this lesson
compare JDBC, jOOQ, and JPA and justify a choice.
Planned topics
- JDBC /
JdbcClient/JdbcTemplate: full control, minimal dependencies, manual mapping and no compile-time checks. - jOOQ: type-safe SQL, great for reports and complex queries; you manage writes and mapping yourself.
- JPA: productivity for CRUD and aggregates; the cost is hidden SQL and the learning curve.
- Decide per use case: team skill, query complexity, write shape, performance needs.
- Mixing is fine if each module has one approach and transaction management is shared.
Draft outline details
Demonstration
a decision table with columns: use case, complexity, writes/reads, choice, reason.
Check your understanding
Which tool for a 10-join report with window functions?
Show answer
jOOQ, or plain SQL, rather than JPA.
Practice
Apply this lesson with the module's lab, exercises and quiz.
Marking a lesson complete is optional and you can undo it any time. Your progress stays in this browser.