(Offtopic)
Hey axilmar - I found your comment on a different thread[0] really interesting, and would love to chat with you about it. Couldn't find your contact details.
Would you be open to emailing me? My email is on my profile.
PS: Not a hiring / sales attempt.
At my previous company, we implemented basic audit trails using postgres triggers that recorded the before & after state of a row on upsert / delete. The triggers had to be set individually for each of the tables (same trigger function worked for all), and an added convenience view to see the diff of the changes helped. This worked pretty well us, since we didn't need details of the actor / IP address etc.
Shameless plug: my project Revamp (https://revamphq.com) attempts to solve the same problem as this.
Still in very early stages though - would love to talk if you find it interesting.
Using Revamp, you can continue building on top of your existing stack while also allowing non-developers to make changes and deploy them immediately.
Currently in beta.
We're building a way to use caching across more types of APIs which might have previously been considered non-cacheable.
This blog is a recap on how we stumbled on this solution.
Would love to hear your thoughts.