JPA Inheritance | Avoid Audit Field Duplication In Enterprise API Systems

Auditing is a cross cutting concern which spreads across all the transactions of an API, and when audit fields defined on each entity such as created-by, updated-by, created-on etc. it will lead to code duplication and inconsistencies when each entity begins to maintain their own naming conventions and audit fields.

This will cause many issues when consuming the audit information for troubleshooting or over central analytics system.

I talked about separating all the audit fields from entities of all the microservices on to a sharable library using JPA provided inheritance features.

Technologies and Tools:

- Java, SpringBoot
- JPA Inheritance
- AspectJ AoP
- Spring Configuration Server
- Maven

GIT Repos :

Related Other Videos: