Add jdbc-vs-jpa module: Spring Data JDBC vs JPA on a shared Order aggregate
Same Customer/Order/OrderItem domain modelled with Hibernate/Spring Data JPA and Spring Data JDBC side by side, both running through a shared StatementLoggingDataSource so SQL-statement counts are directly comparable. 11 tests, 11 captured transcripts, 6 doc chapters. Companion repo for the ankurm.com article on when to drop the ORM.
This commit is contained in:
@@ -15,9 +15,11 @@
|
||||
An aggregator only. Each module declares its own spring-boot-starter-parent, deliberately:
|
||||
|
||||
migration-behavior Spring Boot 4.0.6 / JDK 21: the versions the four published
|
||||
migration articles were written and verified against. Upgrading it
|
||||
would silently invalidate output those articles quote.
|
||||
transactions Spring Boot 4.1.1 / JDK 25, current at the time of writing.
|
||||
migration articles were written and verified against. Upgrading it
|
||||
would silently invalidate output those articles quote.
|
||||
transactions Spring Boot 4.1.1 / JDK 25, current at the time of writing.
|
||||
jdbc-vs-jpa Spring Boot 4.1.1 / JDK 25. Same domain modelled with Spring Data JPA
|
||||
and Spring Data JDBC side by side, for the "when to drop the ORM" article.
|
||||
|
||||
Keeping them apart costs one extra pom and means neither article's evidence rots when the
|
||||
other module moves on.
|
||||
@@ -25,5 +27,6 @@
|
||||
<modules>
|
||||
<module>migration-behavior</module>
|
||||
<module>transactions</module>
|
||||
<module>jdbc-vs-jpa</module>
|
||||
</modules>
|
||||
</project>
|
||||
|
||||
Reference in New Issue
Block a user