4 ms·
> we're doing some work soon to remove the audit table from the database Out of pure curiosity, what are you replacing it with (if anything)? Just a simple rot
by clessg 5y ago
> we're doing some work soon to remove the audit table from the database
Out of pure curiosity, what are you replacing it with (if anything)? Just a simple rotating log file?
- mrbabbage 5y agoExact strategy to be determined—we're looking at various data layers at the moment. I wish we could do something simple like a rotating log file, but we want to be able to query it in the app (for instance, to show recent logins).
- clessg 5y agoVery interesting! Looking forward to the next blog post on that ;)
- jamesrr39 5y agoHave you considered an OLAP database like Clickhouse or QuestDB? An OLAP database would be a much better fit for audit tables given the read and append-only writing requirements, would compress better, and you might be able to fit it directly without changing any app code with a Postgresql foreign data wrapper.
- lillecarl 5y agoI was thinking TimescaleDB
- icheishvili 5y agoYou can partition your audit/event table by time period and archive old events [1] or you can avoid the records hitting the database in the first place by generating the events elsewhere to begin with [2]. [1] https://github.com/icheishvili/audit-trigger https://github.com/icheishvili/audit-trigger [2] https://github.com/eulerto/wal2json https://github.com/eulerto/wal2json