The application i'm currently working on requires every made to the database be audited in another table:
ex: Employee Table has EmployeeAuditTable
I've been debating on where i should put the auditing functionality! Following DDD could anyone offer me their advice and opinion.
The options that come to mind to me are the following 1.) When a "Repository" calls save changes, i should perform the auditing logic from the repository ( Is this bad design/practice to have the Repository not …