bill-kotlin-code-review-persistence

To review Kotlin persistence, you examine repository and DAO modules to validate transaction boundaries, verify ORM mapping consistency, and check migrations for data loss risks before merging high-risk persistence changes.

Transaction boundary validation ensures atomicity and correct commit/rollback behavior across repositories and DAOs. It detects data integrity risks by verifying transactional scopes prevent partial writes, race conditions, and non-idempotent operations.

Checking migration safety involves reviewing schema changes for nullability constraints, data loss, and rollout compatibility. You audit migration scripts to ensure schema updates do not break ORM mappings or compromise persistence integrity.

You detect race conditions and lost updates by verifying ORM and SQL mapping consistency between Kotlin entities and database schemas. This surfaces non-idempotent writes and stale read risks to maintain data integrity.

You need a persistence review whenever a Kotlin service touches persistence layers. Run it to surface high-risk changes in repositories, DAOs, and migrations before merging, ensuring transactional boundaries and tenant filters are enforced.

Yes, the review enforces requirements for tenant filters and deterministic reporting. It audits Kotlin persistence modules to identify tenant-filter gaps and ensure deterministic behavior across transaction boundaries and ORM layers.