wasmer.io VS temporal_tables

The funny thing is that you can actually check for these things if you go beyond the shitposting, as all our work in the website is actually done in the open: https://github.com/wasmerio/wasmer.io (check the history for the pages, if you know how to code it should be easy to spot!)

This is awesome. I was looking for something similar (either fully static or a headless CMS) for using it on the Wasmer website blog [1], which is already using Next.js.

We'll give it a try... thanks for the great work!

[1]: https://github.com/wasmerio/wasmer.io

The article lives here: https://github.com/wasmerio/wasmer.io/blob/master/_posts/wasm-as-universal-binary-format-part-1-native-executables.md

It was reimplemented in pure SQL here https://github.com/nearform/temporal_tables for this purpose

I enjoyed this blog. I think it provides a great succinct overview of various approaches native to Postgres.

For the "capture changes in an audit table" section, I've had good experiences at a previous company with the Temporal Tables pattern. Unlike other major RDBMS vendors, it's not built into Postgres itself, but there's a simple pattern [1] you can leverage with a SQL function.

This allows you to see a table's state as of a specific point in time. Some sample use cases:

- "What was this user's configuration on Aug 12?"

- "How many records were unprocessed at 11:55pm last night?"

- "Show me the diff on feature flags between now and a week ago"

[1]: https://github.com/nearform/temporal_tables

One of these Postgres-based implementations of SQL:2011's temporal versioning features might get you close enough:

- https://github.com/nearform/temporal_tables

You don't really need to install an extension to use temporal tables, there is an alternative (https://github.com/nearform/temporal_tables) implemented purely as a plpgsql trigger so that it works everywhere.

I was part of a team at NearForm using this for a project on an EC2 instance. In order to move to AWS RDS we had to recreate the functionality of temporal_tables as a PostgreSQL function, rather than extension.

When we switched, we found that although there were minor bugs, we didn't have any noticeable loss of performance and we have used it ever since for many projects.

https://github.com/nearform/temporal_tables

If you're also limited by cloud services and the extensions limitations, this is a great solution.