Ask HN: Should you use DB trigger to implement Audit Log?
I mean I get it, DB trigger is easy to use.
But, isn't Audit Log supposed to be consumed by customers directly? Hence it's a domain entity. And DB table is implementation detail that may or may not corelate to domain entity?
It looks to me, using DB trigger for audit log is a terrible idea. So why should we use DB trigger to implement audit log? Or, if it's obviously wrong, then why would so many articles support the idea?